-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update docs to reflect OAuth client credentials may be used instead of an API key #150
Comments
Thanks for the update @passcod ! Adding this to our project backlog. |
Hmm, this should be supported already, as support landed in the terraform provider version 0.13.7. Indeed I can see this in the generated pulumi sdk code. So it might just work already, and only need documenting. I'll try it out later this weekend and report back. |
@passcod looks like you're correct – I'll change this issue to track updating our docs. Thanks for checking! |
Can confirm setting |
Hi everyone - looking into this further, it appears that we have a failed release run for v0.12.1: https://github.com/pulumi/pulumi-tailscale/actions/runs/4632658057 which means we don't need to update our docs; we just need to ensure that the publish step succeeds. |
Hi @passcod - many thanks for the tip on OAuth clients 👍 |
Hello!
Issue details
Tailscale now supports (in beta) OAuth access which notably doesn't expire, and is tied to the tailnet, not a user. This would stop this provider needing its credentials rotated every 90 days!
Also would permanently solve #93 I think ;)
Affected area/feature
The text was updated successfully, but these errors were encountered: