Skip to content

KEH-2171: Assume Service Role via SSO#19

Open
hadiqur wants to merge 11 commits into
mainfrom
KEH-2171-Assume-Service-Role-SSO
Open

KEH-2171: Assume Service Role via SSO#19
hadiqur wants to merge 11 commits into
mainfrom
KEH-2171-Assume-Service-Role-SSO

Conversation

@hadiqur
Copy link
Copy Markdown
Contributor

@hadiqur hadiqur commented May 21, 2026

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

What

The IAM role for this service can now be assumed via SSO for the most secure development experience.

Testing

Have any new tests been added as part of this issue? If not, try to explain why test coverage is not needed here.

  • Yes
  • No
    Please write a brief description of why test coverage is not necessary here.
  • Not as part of this ticket. (Could be done at a later point)

Documentation

Has any new documentation been written as part of this issue? We should try to keep documentation up to date
as new code is added, rather than leaving it for the future.

  • Yes
  • No
    Please write a brief description of why documentation is not necessary here.
  • Not as part of this ticket. (Could be done at a later point)

Related issues

N/A

How to review

Check that instructions in updated README to run the service make sense. If you wish, you may also follow the updated instructions itself to run the service.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 21, 2026

⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ ACTION actionlint 4 0 0 0.06s
✅ ACTION zizmor 4 0 0 2.17s
⚠️ BASH bash-exec 4 2 0 0.01s
✅ BASH shellcheck 4 0 0 0.07s
✅ BASH shfmt 4 0 0 0.0s
✅ DOCKERFILE hadolint 1 0 0 0.04s
✅ REPOSITORY checkov yes no no 25.39s
✅ REPOSITORY gitleaks yes no no 5.3s
✅ REPOSITORY git_diff yes no no 0.01s
✅ REPOSITORY grype yes no no 44.21s
✅ REPOSITORY osv-scanner yes no no 0.46s
✅ REPOSITORY secretlint yes no no 0.85s
✅ REPOSITORY syft yes no no 1.46s
✅ REPOSITORY trivy yes no no 13.53s
✅ REPOSITORY trivy-sbom yes no no 0.3s
✅ REPOSITORY trufflehog yes no no 2.25s
✅ YAML prettier 8 0 0 0.47s
✅ YAML v8r 8 0 0 5.25s
✅ YAML yamllint 8 0 0 0.6s

Detailed Issues

⚠️ BASH / bash-exec - 2 errors
Results of bash-exec linter (version 5.3.3)
See documentation on https://megalinter.io/9.5.0/descriptors/bash_bash_exec/
-----------------------------------------------

❌ [ERROR] concourse/scripts/assume_role.sh
    Error: File:[concourse/scripts/assume_role.sh] is not executable

✅ [SUCCESS] concourse/scripts/build_image.sh
✅ [SUCCESS] concourse/scripts/set_pipeline.sh
❌ [ERROR] concourse/scripts/terraform_infra.sh
    Error: File:[concourse/scripts/terraform_infra.sh] is not executable

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@9.5.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,ACTION_ZIZMOR,BASH_EXEC,BASH_SHELLCHECK,BASH_SHFMT,DOCKERFILE_HADOLINT,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_GRYPE,REPOSITORY_OSV_SCANNER,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository

@hadiqur hadiqur requested a review from a team May 21, 2026 15:54
@hadiqur hadiqur self-assigned this May 21, 2026
@hadiqur hadiqur added the enhancement New feature or request label May 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant