feat: allow secrets collector to retreive all key data if specified #1801
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.
Description
This PR adds a new
includeAllData
field to the secrets collector that allows collecting all key-value pairs from a Kubernetes secret, similar to the existing functionality in the ConfigMap collector.Problem
Previously, the secrets collector could only:
key
+includeValue
Users requested the ability to collect all key-value pairs from a secret without having to specify each key individually.
Solution
Added
includeAllData
boolean field that when set totrue
:data
map with all secret key-value pairs (converted from[]byte
tostring
)includeAllData
take precedence over key-specific collectionChecklist
Does this PR introduce a breaking change?
Usage Examples
Output Format
With
includeAllData: true
, the JSON output includes adata
field:Traditional key-specific collection remains unchanged: