Skip to content

feat(harbor-scanner-sysdig-deploy): Allow cliScanning SECRET_NAME to be Configurable #2247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

sthwang-metal
Copy link
Contributor

@sthwang-metal sthwang-metal commented May 12, 2025

Signed-off-by: Stephen Hwang 126002920+sthwang-metal@users.noreply.github.com

What this PR does / why we need it:

This allows the jobs spun up when cliScanning is enabled to use a secret with a different name than 'harbor-scanner-sysdig-secure.fullname'. This is useful if there is a secret defined with the same name for a different purpose.

Checklist

  • Title of the PR starts with type and scope, (e.g. feat(agent,node-analyzer,sysdig-deploy):)
  • Chart Version bumped for the respective charts
  • Variables are documented in the README.md (or README.tpl in some charts)
  • Check GithubAction checks (like lint) to avoid merge-check stoppers
  • All test files are added in the tests folder of their respective chart and have a "_test" suffix

Copy link
Contributor

Hi @sthwang-metal. Thanks for your PR.

After inspecting your changes someone with write access to this repo needs
to approve and run the workflow.

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR title does not comply with regex: ^(\w*)(?:\(([\w\$\.\,\-\*\s]*)\))?\:\s?(.*)$!
Check PR guidelines at https://github.com/sysdiglabs/charts/blob/main/README.md#pull-requests

@sthwang-metal sthwang-metal changed the title allow cliScanning SECRET_NAME to be configurable feat(harbor-scanner-sysdig-deploy): Allow cliScanning SECRET_NAME to be Configurable May 12, 2025
@github-actions github-actions bot dismissed their stale review May 12, 2025 18:48

All good!

@sthwang-metal sthwang-metal force-pushed the make-cliScanning-secret-configurable branch 2 times, most recently from 0f5bac8 to d82756d Compare May 12, 2025 18:58
@sthwang-metal sthwang-metal marked this pull request as ready for review May 12, 2025 19:59
sthwang-metal and others added 2 commits May 15, 2025 08:56
@mavimo mavimo force-pushed the make-cliScanning-secret-configurable branch from abcbe94 to 7dd3549 Compare May 15, 2025 06:56
@mavimo
Copy link
Contributor

mavimo commented May 15, 2025

Hey @sthwang-metal thanks for your contribution! I added some test to cover the use case you added and made few minor changes, once test are executed i'll approve 🙌

@dark-vex
Copy link
Collaborator

Hey @sthwang-metal we had an issue in merging this PR so I've created a new one (#2254) by cherry-pick your's and Marco's commits. I close this one, thanks a lot for your contribution

@dark-vex dark-vex closed this May 16, 2025
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.

3 participants