Open jfeng-dev opened 3 years ago
A proposal for the pairing_key argument to be available not only for type PARTNER
for the google_compute_interconnect_attachment
resource.
Note: https://github.com/GoogleCloudPlatform/magic-modules/pull/4480 looks like a feasible solution, but it stalled out due to CLA. Someone may be able to just carry that work forward.
Community Note
Description
I'm willing to do the work for this in the Magic Modules
The terraform provider doesn't support an input for the
pairing_key
field whentype
isPARTNER_PROVIDER
, thoughtype
supports valuePARTNER_PROVIDER
currently. Terraform Doc GCP DocThere could be a new input key
partner_pairing_key
to avoid theCOMPUTED + OPTIONAL
issue that might come up ifpairing_key
was optional input and sometimes output or empty. Would this be the right path to go down?The use case would be provisioning interconnect attachments as a Partner Provider. It would complete the workflow initiated by the current
PARTNER
functionality set up. Admittedly, it's fairly niche.We might have access to a Partner Interconnect for testing in a few weeks.
New or Affected Resource(s)
Potential Terraform Configuration
References
https://github.com/hashicorp/terraform-provider-google/issues/4326 https://github.com/GoogleCloudPlatform/magic-modules/pull/1323 https://github.com/hashicorp/terraform/issues/21278
b/359561794