Skip to content

feat(shield): migrate feature keys to host-shield.yaml #2159

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

aroberts87
Copy link
Collaborator

As the host-shield.yaml file has introduced new keys, we are now able to migrate those feature settings from the legacy dragent.yaml file to the new format.

This change also takes the opportunity to clean up a few areas around related helper function use where relevant.

What this PR does / why we need it:

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

As the host-shield.yaml file has introduced new keys, we are
now able to migrate those feature settings from the legacy
dragent.yaml file to the new format.

This change also takes the opportunity to clean up a few areas
around related helper function use where relevant.
@aroberts87 aroberts87 self-assigned this Feb 24, 2025
@aroberts87 aroberts87 requested a review from a team as a code owner February 24, 2025 18:21
Copy link
Contributor

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale The issue or pull request is inactive and will be closed soon label Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale The issue or pull request is inactive and will be closed soon
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants