Closed daniel-cit closed 4 months ago
I suspect this could result in a race condition with other PRs/Repos. But especially between terraform-example-foundation-int-trigger-HubAndSpoke
terraform-example-foundation-int-trigger-default
as they are trigger at the same time for a PR?
I suspect this could result in a race condition with other PRs/Repos. But especially between
terraform-example-foundation-int-trigger-HubAndSpoke
terraform-example-foundation-int-trigger-default
as they are trigger at the same time for a PR?
@apeabody
The normal configuration of the test org is to have an access context manager policy ID.
The policy ID is removed when an integration build for the repo terraform-google-vpc-service-controls runs a helper script.
an alternative would be to create the access context manager policy ID using gcloud
or a helper script but not using the foundation Terraform configuration on step 1-org and this would run in only one of the two test flows.
This would fix the situation the first time the chosen test flow runs.
I suspect this could result in a race condition with other PRs/Repos. But especially between
terraform-example-foundation-int-trigger-HubAndSpoke
terraform-example-foundation-int-trigger-default
as they are trigger at the same time for a PR?@apeabody
The normal configuration of the test org is to have an access context manager policy ID.
The policy ID is removed when an integration build for the repo terraform-google-vpc-service-controls runs a helper script.
an alternative would be to create the access context manager policy ID using
gcloud
or a helper script but not using the foundation Terraform configuration on step 1-org and this would run in only one of the two test flows.This would fix the situation the first time the chosen test flow runs.
Yeah - A Terraform resource exists error would be unrecoverable, but a gcloud.Runf
to create in org_test.go
could simply "fail" ok without needing complex pre-conditions. Anyway, just a thought to limit test failures.
@apeabody Could you PTAL again
This PR will toggle the creation of the access context manager policy ID in the test in step 1-org if it does not exist in the organization.
This will fix this errors in integration test
and