Allow to pass the whole alloy config as Sensitive #7
Conversation
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
dabelenda
force-pushed
the
sensitive_config
branch
from
ab43ad9 to
9322b1c
Compare
dabelenda
force-pushed
the
sensitive_config
branch
from
9322b1c to
e63718c
Compare
evgeni
approved these changes
May 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Pull Request (PR) description
The alloy configuration contains a lot of sensitive data that might not be wanted in PuppetDB or the logs of the agent.
Passing the configuration contents as Sensitive will allow to exclude this content from both.
This Pull Request (PR) fixes the following issues
Fixes !5