-
Notifications
You must be signed in to change notification settings - Fork 10
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
Changing the github token in the stack config doesn't have any effect #203
Comments
Hi @pierskarsenbarg - I attempted to repro this and it turns out it is only Console output after setting the secret:
I did not see any differnece between setting the token as an env var or via |
This is an instance of pulumi/pulumi#4981. |
By setting the token via an env var: |
Hello!
Issue details
It looks like we store the (encrypted) GitHub token in the stack as part of the provider and if the token is changed in the stack config we don't update the value. This means that if the original token no longer exists (if it expires or is deleted) then you can't perform any more updates.
Steps to reproduce
pulumi config set github:token <token> --secret
)pulumi up
pulumi refresh
(You can also run
pulumi stack export
after step 5 and then see that it doesn't update in the stack json)Expected: Pulumi would use the new access token
Actual: Pulumi continues to use the old (deleted) access token as part of the provider.
The text was updated successfully, but these errors were encountered: