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

Add billingType attribute to Apigee Organization resource #11226

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

Some customers are requesting to explicitly control the billingType attribute of the Apigee organization resource instead of relying on Apigee to set the appropriate one.

New or Affected Resource(s)

  • google_apigee_organization

Potential Terraform Configuration

# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.
    - !ruby/object:Api::Type::String
      name: 'billingType'
      description: |
        Billing type of the Apigee organization. See [Apigee pricing](https://cloud.google.com/apigee/pricing).
      default_value: "BILLING_TYPE_UNSPECIFIED"
      input: true

References

@xuchenma
Copy link

xuchenma commented Mar 8, 2022

Made a PR for this: GoogleCloudPlatform/magic-modules#5796

@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 Apr 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.