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

fix: read metal-go client's auth token from config, not env #433

Merged
merged 1 commit into from
Oct 31, 2023

Conversation

ctreatma
Copy link
Contributor

When the metal-go client was introduced to enable packngo deprecation, it was wired up directly to the METAL_AUTH_TOKEN environment variable for auth. This breaks auth when a customer is using the auth_token provider configuration.

This updates the metal-go client initialization so that the client will work with both the auth_token setting and the METAL_AUTH_TOKEN env var.

When the metal-go client was introduced to enable packngo deprecation,
it was wired up directly to the `METAL_AUTH_TOKEN` environment variable
for auth.  This breaks auth when a customer is using the `auth_token`
provider configuration.

This updates the metal-go client initialization so that the client will
work with both the `auth_token` setting and the `METAL_AUTH_TOKEN` env
var.
@ctreatma ctreatma temporarily deployed to internal October 31, 2023 14:45 — with GitHub Actions Inactive
@displague displague merged commit d347d05 into main Oct 31, 2023
4 of 5 checks passed
@displague displague deleted the metal-go-auth-token branch October 31, 2023 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants