-
Notifications
You must be signed in to change notification settings - Fork 135
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
[FEATURE] Support access_token
based provider authentication
#660
Comments
Hello @0x416e746f6e, thanks for opening this issue. This seems like a good idea indeed. We'll work on it whenever possible and keep you posted here ! |
@amstuta if that helps I have a working patch on my machine. Can send a PR (for both of the repos). Unfortunately, I am stuck on some strange issue when the access token fails to access
Do you know why could that be? (The underlying client has |
Yes you can push a PR first on go-ovh, we'll be happy to review it :) About the |
@0x416e746f6e thanks for your contribution on go-ovh, |
Description
It would be great if this provider would directly support
access_token
authentication mechanism.This could enable the pattern of using hashicorp vault oauth2 secret-engine to generate short-lived tokens for terraform, so that we don't need to maintain static credentials (on allow them to be remembered inside terraform state-files if they are retrieved via data-source from somewhere).
Affected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: