[processor/resourcedetection] Fix consul TokenFile using path as token value#46746
Merged
Conversation
…h as token value Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
github-actions
Bot
added
the
processor/resourcedetection
Member
Author
|
/rerun |
paulojmdias
changed the title
dashpole
approved these changes
Mar 11, 2026
paulojmdias
added
ready to merge
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
4 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.
Description
When
token_filewas configured, the file path string was assigned toapi.Config.Tokeninstead ofapi.Config.TokenFile, causing the consul API client to use the path as the authentication token.Link to tracking issue
Fixes #46745
Testing
Added unit tests.