-
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
Track Apigee Organization Properties #10083
Track Apigee Organization Properties #10083
Comments
We are managing quite some apigee orgs with terraform. After some troubleshooting it turns out this issue is breaking our setup from time to time. Is there any progress on finding a solution for this bug? |
Hi @bartdw, thanks for the +1. We are still looking into this. Until the fix is in place, the recommended approach for you would be to use the lifecycle attributes to ignore changes on the Apigee Organization resource and treat it as immutable to prevent the resource from breaking your setup. |
Trying to fix this by GoogleCloudPlatform/magic-modules#5556 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
Terraform apply removes non-default Apigee org properties.
From what I gathered so far:
Terraform provider mmv1 does not have the Apigee org properties defined that are set on the Apigee Org API resource e.g. :
as a TF resource property and therefore updates reset the properties on the organization. This currently removes the features.mart.connect.enabled property that is required for Apigee hybrid.
New or Affected Resource(s)
Potential Terraform Configuration
Add the
references
field to the mmv1 config.References
The text was updated successfully, but these errors were encountered: