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

Integ tests/examples of environment resource collide and fail #296

Closed
IaroslavTitov opened this issue Jun 4, 2024 · 2 comments
Closed
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Milestone

Comments

@IaroslavTitov
Copy link
Contributor

What happened?

When 2 workflows running integ tests at the same time, the names of the environments collide and make tests fail. It requires manually deleting environments after and restarting the workflow.

Example

https://github.com/pulumi/pulumi-pulumiservice/actions/runs/9371106250/job/25799773295

error: [409] Conflict: a environment with name "testing-environment-cs" already exists

Output of pulumi about

Not relevant

Additional context

Fix this the same way schedule resource collision is fixed - appending digits (random number) to the end of the name.

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).

@IaroslavTitov IaroslavTitov added the kind/bug Some behavior is incorrect or out of spec label Jun 4, 2024
@IaroslavTitov IaroslavTitov self-assigned this Jun 4, 2024
@IaroslavTitov IaroslavTitov added this to the 0.105 milestone Jun 4, 2024
@IaroslavTitov
Copy link
Contributor Author

Fixed with #307, closing

@pulumi-bot
Copy link

Cannot close issue:

  • does not have required labels: resolution/

Please fix these problems and try again.

@IaroslavTitov IaroslavTitov added the resolution/fixed This issue was fixed label Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

2 participants