hashicorp / terraform-provider-google

Terraform Provider for Google Cloud Platform
https://registry.terraform.io/providers/hashicorp/google/latest/docs
Mozilla Public License 2.0
2.32k stars 1.73k forks source link

"google_apigee_instance" should support a "peering_cidr_range" values from /16 through /20 #10112

Closed jaredweeks closed 2 years ago

jaredweeks commented 3 years ago

Community Note

Description

Apigee paid org runtime instances now support provisioning with any peering CIDR range from /16 through /20. My company needs to provision various sized runtime instances to meet our needs. Currently we can't do this in Terraform and need to break the instance create code into shell scripting and making the calls through the API via CURL. Not ideal.

New or Affected Resource(s)

Potential Terraform Configuration

resource "google_apigee_instance" "apigee_instance_us_east4" { depends_on = [ google_kms_crypto_key_iam_binding.apigee_sa_keyuser_runinst ]
name = "us-east4" location = "us-east4" description = "Terraform-managed Apigee Runtime Instance USEAST4" display_name = "us-east4" org_id = google_apigee_organization.org.id peering_cidr_range = "SLASH_18" disk_encryption_key_name = google_kms_crypto_key.apigee_cryptokeyruninst_us4.id }

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

References

matt-hottinger commented 2 years ago

Hey @ScottSuarez, could you provide a general timeline for when this will be published in a future release?

ScottSuarez commented 2 years ago

This should be released today

github-actions[bot] commented 2 years ago

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.