-
Notifications
You must be signed in to change notification settings - Fork 7
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
Calling pulumiservice.TeamAccessToken()
with --refresh
causes token name conflict and update failure
#159
Comments
This was fixed by #177 |
Cannot close issue:
Please fix these problems and try again. |
Hi @komalali. I don't believe this is resolved by #177. My project is what @aureq's original reproduction was copied from and I still am seeing the provider wanting to recreate existing tokens when using
Thanks! |
Whoops sorry about that @theplatformer - you're totally right, that PR only touched the |
This should be fixed in the latest release, v0.15.0 - feel free to reopen if the issue isn't resolved! |
Thanks @komalali. Unfortunately it is still wanting to
Interestingly, running the preview with
Reverting back to |
🤦🏽 Yikes! Apologies for the back and forth here. I am able to repro the issue you're seeing with |
All good @komalali! Appreciate the efforts 🙇 |
@theplatformer pushing out a new release now - but I'm slightly concerned about the fact that |
@komalali No luck unfortunately, though things have changed a little.
I don't have a theory as to why the fifth token isn't showing as a This is an example of the
There was a support ticket (#3353) from when I originally hit the issue but I believe it has been closed now. It might be easier to touch base over Slack? @aureq could you maybe make an intro? Thanks! |
What happened?
When using this provider, a customer can create a Pulumi app to efficiently manage Team Access Tokens.
However, if during a subsequent update
--refresh
is used, Pulumi will attempt to recreate a token that already exists. As a result to this, the update fails with the errorfailed to create access token: 409 API error: Conflict: token name already exists
because a token with the same name already exists.Expected Behavior
The team access token is create during the 1st deployment, then no further update is needed even when calling
pulumi up --refresh
.Steps to reproduce
pulumi new typescript
npm install --save @pulumi/pulumiservice @pulumi/random
index.ts
provided belowpulumi up --yes
and a new team access token is created ✅pulumi up --yes
and nothing gets updated ✅pulumi up --yes --refresh
, the update attempts to create a new team access token and subsequently fails ❌Output of
pulumi about
Additional context
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: