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

Chore: move env test is flaky - use never deployed env #943

Merged
merged 2 commits into from
Aug 26, 2024

Conversation

chpl
Copy link
Contributor

@chpl chpl commented Aug 26, 2024

Issue & Steps to Reproduce / Feature Request

the test is flaky - often fails with

│ Error: failed to move environment to project id 'e46ce3e9-79b5-4e4d-bba9-1d9b9f252155': 400 Bad Request: cannot move environment while in progress. id: 4cc847e7-c45d-4389-b49d-4e9bdf94f80a

(was added in #939)

Solution

use never deployed environment

@chpl chpl changed the title move env test - use never deployed env Chore - move env test is flaky - use never deployed env Aug 26, 2024
@chpl chpl requested a review from a team August 26, 2024 09:39
Copy link

@yarivg yarivg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems good

@@ -55,7 +55,7 @@ resource "env0_environment" "example" {
depends_on = [env0_template_project_assignment.assignment]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this environment still necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes. tomer just added the move part here

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the original purpose of the test was to test different types / settings of environments, and here there was an attempt to kill 2 birds with one stone by testing both regular deployment and move environment. so I think it is still needed for the original purpose

@github-actions github-actions bot added the ready to merge PR approved - can be merged once the PR owner is ready label Aug 26, 2024
@chpl chpl changed the title Chore - move env test is flaky - use never deployed env Chore: move env test is flaky - use never deployed env Aug 26, 2024
@chpl chpl merged commit 00a265f into main Aug 26, 2024
8 of 9 checks passed
@chpl chpl deleted the chore-move-env-test branch August 26, 2024 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore integration-tests ready to merge PR approved - can be merged once the PR owner is ready
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants