Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vault: configure user agent on Nomad vault clients #15745

Merged
merged 2 commits into from
Jan 10, 2023
Merged

Conversation

shoenig
Copy link
Member

@shoenig shoenig commented Jan 10, 2023

This PR attempts to set the User-Agent header on each Vault API client
created by Nomad. Still need to figure a way to set User-Agent on the
Vault client created internally by consul-template.

Partial of #15629

This PR attempts to set the User-Agent header on each Vault API client
created by Nomad. Still need to figure a way to set User-Agent on the
Vault client created internally by consul-template.
Comment on lines 356 to 355
// Set the token in the API client to the one that needs
// SetHeaders the token in the API client to the one that needs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this a find-and-replace gone wild? There are some others like this in nomad/vault.go as well 😅

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah crap, I dunno how I didn't see this

helper/useragent/useragent.go Show resolved Hide resolved
@shoenig shoenig merged commit f05aa6d into main Jan 10, 2023
@shoenig shoenig deleted the b-set-useragent-more branch January 10, 2023 16:39
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants