Implement OTEL secrets replacement in parsed policy#6419
Open
michel-laterman wants to merge 1 commit intoelastic:mainfrom
Open
Implement OTEL secrets replacement in parsed policy#6419michel-laterman wants to merge 1 commit intoelastic:mainfrom
michel-laterman wants to merge 1 commit intoelastic:mainfrom
Conversation
Added functionality to replace secrets in OTEL sections (receivers, exporters, processors, extensions, connectors) of a policy. Updated the `NewParsedPolicy` function to process these sections and append identified secret keys. Included a new test case to validate the correct replacement of secrets in the OTEL sections.
michel-laterman
added
Team:Elastic-Agent-Control-Plane
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the problem this PR solves?
Added functionality to replace secrets in OTEL sections (receivers, exporters, processors, extensions, connectors) of a policy. Updated the
NewParsedPolicyfunction to process these sections and append identified secret keys. Included a new test case to validate the correct replacement of secrets in the OTEL sections.How does this PR solve the problem?
Add a call to the existing
ProcessMapSecretsmethod for OTEL keys in the policy.Design Checklist
I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration files./changelog/fragmentsusing the changelog toolRelated issues