Skip to content

Conversation

@kubabuczak
Copy link
Collaborator

Description

What does this PR have in it?

Key Changes

Highlight the updates in specific files

Testing and Verification

How did you test these changes? What automated tests are added?

Related Issues

Jira tickets, GitHub issues, Support tickets...

PR Checklist

  • Code changes adhere to the project's coding standards.
  • Relevant unit and integration tests are included.
  • Documentation has been updated accordingly.
  • All tests pass locally.
  • The PR description follows the project's guidelines.

…of static credentials

- Replaced aws-actions/configure-aws-credentials@v1 with v5 across multiple workflows.
- Updated AWS credential configuration to use role-based access with role-to-assume and role-session-name.
- Added permissions for contents, packages, and pull-requests in several workflows.
…ase branch

- Added CSPL-4201-pipeline-tests-base branch to the trigger conditions for multiple workflows including build-test-push, distroless integration tests, helm tests, and various integration tests for Azure and GCP.
@kubabuczak kubabuczak force-pushed the CSPL-4201-trigger-pipeline branch from 8777f51 to 6d72713 Compare November 17, 2025 14:13
@kubabuczak kubabuczak marked this pull request as draft November 17, 2025 17:49
@coveralls
Copy link
Collaborator

coveralls commented Nov 17, 2025

Pull Request Test Coverage Report for Build 19700919165

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage decreased (-0.008%) to 86.544%

Files with Coverage Reduction New Missed Lines %
pkg/splunk/enterprise/cp.go 1 33.33%
Totals Coverage Status
Change from base Build 19700908906: -0.008%
Covered Lines: 10709
Relevant Lines: 12374

💛 - Coveralls

@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 19432520209

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 86.552%

Totals Coverage Status
Change from base Build 19432580421: 0.0%
Covered Lines: 10710
Relevant Lines: 12374

💛 - Coveralls

…eout settings

- Added role-duration-seconds parameter to AWS credential configurations across multiple workflows.
- Increased timeout settings for integration and smoke tests to 420 minutes and 360 minutes respectively in various workflows.
@kubabuczak kubabuczak force-pushed the CSPL-4201-trigger-pipeline branch from 6d72713 to 3e0fb55 Compare November 19, 2025 11:15
- Added 'id-token: write' permission to the build-test-push workflow for enhanced security and access control.
@kubabuczak kubabuczak force-pushed the CSPL-4201-trigger-pipeline branch from 3e0fb55 to 44fd0d2 Compare November 19, 2025 14:15
@kubabuczak kubabuczak changed the title Update pull request template to clarify related issues section Trigger OIDC pipeline Nov 19, 2025
…bserved values

Reduce timeout settings across multiple GitHub Actions workflows for integration and smoke tests from 360/420 minutes to 240 minutes, optimizing resource usage and execution time.
…redentials

- Added environment variables TEST_S3_ACCESS_KEY_ID and TEST_S3_SECRET_ACCESS_KEY to multiple workflows for integration and smoke tests, allowing for optional overrides of AWS credentials.
- Updated test scripts to utilize these environment variables when creating S3 secrets, enhancing flexibility and security in credential management.
@kubabuczak kubabuczak force-pushed the CSPL-4201-trigger-pipeline branch from 44fd0d2 to 19eb696 Compare November 26, 2025 10:41
@kubabuczak kubabuczak force-pushed the CSPL-4201-pipeline-tests-base branch from b1fcccf to 730e606 Compare November 26, 2025 15:49
@kubabuczak kubabuczak closed this Nov 28, 2025
@kubabuczak kubabuczak deleted the CSPL-4201-trigger-pipeline branch November 28, 2025 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants