Skip to content
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

Comments

@danistrebel
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

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. :

"properties": {
    "property": [
      {
        "name": "features.hybrid.enabled",
        "value": "true"
      },
      {
        "name": "features.mart.connect.enabled",
        "value": "true"
      }
    ]
  }

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)

  • google_apigee_organization

Potential Terraform Configuration

Add the references field to the mmv1 config.

References

@rileykarson rileykarson added this to the Goals milestone Sep 20, 2021
@bartdw
Copy link

bartdw commented Dec 13, 2021

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?

@danistrebel
Copy link
Author

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.

@xuchenma
Copy link

Trying to fix this by GoogleCloudPlatform/magic-modules#5556

@github-actions
Copy link

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.