-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Set config_sync.enabled
field to true
to fix broken tests
#11880
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @zli82016, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
Tests analyticsTotal tests: 11 Click here to see the affected service packages
🟢 All tests passed! View the build log |
mmv1/third_party/terraform/services/gkehub/resource_gke_hub_feature_membership_test.go.tmpl
Outdated
Show resolved
Hide resolved
Terraform google provider v5.41.0 (released on Aug 12, 2024) introduced a new field `config_sync.enabled` to the google_gke_hub_feature_membership resource (b/322551829). The default value of this field is false. However, when the field is omitted from the Terraform resource, Terraform sets the field to false in the ACM Hub API explicitly. This issue causes the Terraform users to fail to install Config Sync unless they set the new field to true explicitly. To mitigate this issue, we enhanced the Hub CLH to throw an error if Config Sync is explicitly disabled and the Git or OCI configuration is set. Our Terraform users need to set the new field to true explicitly to install Config Sync from v5.41.0. For existing CS installations, upgrading from Terraform versions prior to v5.41.0 to versions >= v5.41.0 does not break users, and does not uninstall Config Sync.
f525590
to
6dd1f22
Compare
Tests analyticsTotal tests: 11 Click here to see the affected service packages
🟢 All tests passed! View the build log |
These two tests passed with the fix in this PR. The error for configSync.enabled is addressed for
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for the fixing.
Terraform google provider v5.41.0 (released on Aug 12, 2024) introduced a new field
config_sync.enabled
to the google_gke_hub_feature_membership resource. The default value of this field is false. However, when the field is omitted from the Terraform resource, Terraform sets the field to false in the ACM Hub API explicitly. This issue causes the Terraform users to fail to install Config Sync unless they set the new field to true explicitly.To mitigate this issue, we enhanced the Hub CLH to throw an error if Config Sync is explicitly disabled and the Git or OCI configuration is set.
Our Terraform users need to set the new field to true explicitly to install Config Sync from v5.41.0. For existing CS installations, upgrading from Terraform versions prior to v5.41.0 to versions >= v5.41.0 does not break users, and does not uninstall Config Sync.
part of hashicorp/terraform-provider-google#14591.
Release Note Template for Downstream PRs (will be copied)