Skip to content

Conversation

francesco-furlan
Copy link
Contributor

@francesco-furlan francesco-furlan commented Sep 19, 2025

What this PR does / why we need it:

Add the following configuration to support rapid-response existing secrets:

features
  respond:
    rapid_response:
      # The name of the existing Rapid Response password secret
      password_existing_secret:
      # The key used in the existing Rapid Response secret for the password (default: password)
      password_existing_secret_key:

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

@francesco-furlan francesco-furlan force-pushed the chore/shield-add-rapid-response-password-secrets branch from c983382 to 2ecd27f Compare September 19, 2025 07:31
@francesco-furlan francesco-furlan marked this pull request as ready for review September 24, 2025 12:58
@francesco-furlan francesco-furlan requested a review from a team as a code owner September 24, 2025 12:58
@francesco-furlan francesco-furlan force-pushed the chore/shield-add-rapid-response-password-secrets branch from d35bba0 to 3ec75fc Compare September 24, 2025 13:27
@francesco-furlan francesco-furlan changed the title chore(shield): add support for rapid-response existing_secret feat(shield): add support for rapid-response password_existing_secret Sep 25, 2025
@francesco-furlan francesco-furlan merged commit 29d1f1a into main Sep 25, 2025
7 checks passed
@francesco-furlan francesco-furlan deleted the chore/shield-add-rapid-response-password-secrets branch September 25, 2025 15:00
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