Intermittent test failure in activity-tracker event_routing_settings

[iamar7]

Affected modules

• terraform-ibm-activity-tracker

Terraform CLI and Terraform provider versions

• Terraform version: 1.9.0
• Provider version: v1.78.0

Terraform output

=== NAME  TestRunUpgradeExample
    terraform.go:243: 
        	Error Trace:	/go/pkg/mod/github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper@v1.49.1/testhelper/terraform.go:243
        	            				/go/pkg/mod/github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper@v1.49.1/testhelper/tests.go:541
        	            				/__w/terraform-ibm-activity-tracker/terraform-ibm-activity-tracker/tests/pr_test.go:70
        	Error:      	Should be false
        	Test:       	TestRunUpgradeExample
        	Messages:   	Resource(s) identified to be updated 
        	            	Name: atracker_settings
        	            	Address: module.activity_tracker.ibm_atracker_settings.atracker_settings[0]
        	            	Actions: [update]
        	            	DIFF:
        	            	  Before: 
        	            		{"default_targets":"SECURE_VALUE_HIDDEN_HASH:-2ad78397fafefaf3fc15112fbdcc727ab30f8c44205c5835189a80eb"}
        	            	  After: 
        	            		{"default_targets":"SECURE_VALUE_HIDDEN_HASH:-39db431f3f7c23a02270993c5d7b743da96d2e995c425edd0e78b8c3"}
        	            	
        	            	Change Detail:
        	            	{
        	            	  "actions": [
        	            	    "update"
        	            	  ],
        	            	  "after": {
        	            	    "api_version": 2,
        	            	    "default_targets": "SECURE_VALUE_HIDDEN_HASH:-6cb7e3d3a43e00359f8d7714e79527ee00569751034fb20eb4562df0",
        	            	    "id": "us-south",
        	            	    "message": "Setting audit log can be found in the region it is being called from and the route and target audit logs can be found in the metadata primary region.",

Debug output

Expected behavior

The deployment should have passed without any failure

Actual behavior

The terraform apply failed in the pipeline

Steps to reproduce (including links and screen captures)

1. Run terraform apply

Anything else

---

By submitting this issue, you agree to follow our Code of Conduct

[iamar7]

=== NAME  TestRunUpgradeExample
    terraform.go:243: 
        	Error Trace:	/go/pkg/mod/github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper@v1.49.1/testhelper/terraform.go:243
        	            				/go/pkg/mod/github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper@v1.49.1/testhelper/tests.go:541
        	            				/__w/terraform-ibm-activity-tracker/terraform-ibm-activity-tracker/tests/pr_test.go:70
        	Error:      	Should be false
        	Test:       	TestRunUpgradeExample
        	Messages:   	Resource(s) identified to be updated 
        	            	Name: atracker_settings
        	            	Address: module.activity_tracker.ibm_atracker_settings.atracker_settings[0]
        	            	Actions: [update]
        	            	DIFF:
        	            	  Before: 
        	            		{"default_targets":"SECURE_VALUE_HIDDEN_HASH:-5919b40ad409ee90f285787a0739b3cbfa10ed92efa073e7866e76b8"}
        	            	  After: 
        	            		{"default_targets":"SECURE_VALUE_HIDDEN_HASH:-34eb5fd32042fcc03d9f735955a007d934853ade5b5b8cafbe786506"}
        	            	
        	            	Change Detail:
        	            	{
        	            	  "actions": [
        	            	    "update"
        	            	  ],
        	            	  "after": {
        	            	    "api_version": 2,
        	            	    "default_targets": "SECURE_VALUE_HIDDEN_HASH:-43bf8941ffe814419468c4[2976](https://github.com/terraform-ibm-modules/terraform-ibm-activity-tracker/actions/runs/14825375765/job/41617850111#step:7:2977)8a07925e66b73702c9a5693ba9da33",
        	            	    "id": "us-south",
        	            	    "message": "Setting audit log can be found in the region it is being called from and the route and target audit logs can be found in the metadata primary region.",
        	            	    "metadata_region_backup": null,
        	            	    "metadata_region_primary": "us-south",
        	            	    "permitted_target_regions": "SECURE_VALUE_HIDDEN_HASH:-f620a120f22a5f691a763aa610d913ea5b852f80a2ee1e7faef24ead",
        	            	    "private_api_endpoint_only": false
        	            	  },
        	            	  "after_sensitive": {
        	            	    "default_targets": [
        	            	      false,
        	            	      false,
        	            	      false
        	            	    ],
        	            	    "permitted_target_regions": [
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false
        	            	    ]
        	            	  },
        	            	  "after_unknown": {},
        	            	  "before": {
        	            	    "api_version": 2,
        	            	    "default_targets": "SECURE_VALUE_HIDDEN_HASH:-f243943f31950f7d48692b10e887111aed051ec8caac565cf52f3e24",
        	            	    "id": "us-south",
        	            	    "message": "Setting audit log can be found in the region it is being called from and the route and target audit logs can be found in the metadata primary region.",
        	            	    "metadata_region_backup": null,
        	            	    "metadata_region_primary": "us-south",
        	            	    "permitted_target_regions": "SECURE_VALUE_HIDDEN_HASH:-84a9f7e5711a16f911ba750bc07da45c0df5ccdbea93af2a7f21890d",
        	            	    "private_api_endpoint_only": false
        	            	  },
        	            	  "before_sensitive": {
        	            	    "default_targets": [
        	            	      false,
        	            	      false,
        	            	      false
        	            	    ],
        	            	    "permitted_target_regions": [
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false,
        	            	      false
        	            	    ]
        	            	  }
        	            	}

[ocofaigh]

@iamar7 I think we need to just stop setting any account level settings in the test, or we will keep seeing issues like this

[iamar7]

@iamar7 I think we need to just stop setting any account level settings in the test, or we will keep seeing issues like this

Yes, I will be removing the account level settings from the examples so that the test clash doesn't happen in the pipeline.

[terraform-ibm-modules-ops]

🎉 This issue has been resolved in version 1.0.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀