prometheus.exporter.kafka: use correct secret type #6046
Merged
Conversation
This file contains 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
Use rivertypes.Secret for sensitive fields instead of Prometheus' secret type. Fixes grafana#6044.
thampiotr
approved these changes
Jan 4, 2024
hainenber
pushed a commit
to hainenber/agent
that referenced
this pull request
Jan 6, 2024
Use rivertypes.Secret for sensitive fields instead of Prometheus' secret type. Fixes grafana#6044.
BarunKGP
pushed a commit
to BarunKGP/grafana-agent
that referenced
this pull request
Feb 20, 2024
Use rivertypes.Secret for sensitive fields instead of Prometheus' secret type. Fixes grafana#6044.
github-actions
bot
added
the
frozen-due-to-age
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Use rivertypes.Secret for sensitive fields instead of Prometheus' secret type.
I checked other components for this specific issue and didn't find anything.
Fixes #6044.