sysdiglabs / terraform-google-secure-for-cloud

Terraform module that deploys the Sysdig Secure For Cloud stack in Google Cloud Platform
https://registry.terraform.io/modules/sysdiglabs/secure-for-cloud/google/latest
Apache License 2.0
2 stars 11 forks source link

benchmark collides on subsequent/concurrent testing #44

Open wideawakening opened 3 years ago

wideawakening commented 3 years ago

Same as it happend on AWS (fixed in https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/pull/26) we're getting collision on both simple/org examples, when concurrent testing, on following resources

guess it's low-prio as it would affect only QA

- KO. federation working pool.

β”‚ Error: Error creating service account: googleapi: Error 409: Service account sysdigcloudbench already exists within project projects/integral-legend-204815., alreadyExists
β”‚ 
β”‚   with module.secure-for-cloud_example_organization.module.cloud_bench["integral-legend-204815"].google_service_account.sa,
β”‚   on /home/iru/src/github/terraform-google-cloudvision/modules/services/cloud-bench/main.tf line 50, in resource "google_service_account" "sa":
β”‚   50: resource "google_service_account" "sa" {
β”‚ 

- NOP. sysdig secure cloud account (yeah this is odd.. maybe derived from role collision?)
> this happens because of the backend validation, a benchmark account (cloud-account-sysdig-client) can not be registered more than one

β”‚ Error: 409 Conflict β”‚ β”‚ with module.secure-for-cloud_example_organization.module.cloud_bench["cloudvision-member"].sysdig_secure_cloud_account.cloud_account, β”‚ on /home/iru/src/github/terraform-google-cloudvision/modules/services/cloud-bench/main.tf line 21, in resource "sysdig_secure_cloud_account" "cloud_account": β”‚ 21: resource "sysdig_secure_cloud_account" "cloud_account" { β”‚

nkraemer-sysdig commented 3 years ago

Addressed in https://github.com/sysdiglabs/terraform-google-secure-for-cloud/pull/53