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 internal ipv6 prefix into compute network and subnetwork data source reference attribute #16267

Conversation

modular-magician
Copy link
Collaborator

… datasource

This PR is to make data_source_google_compute_network and data_source_google_compute_subnetwork include internal_ipv6_range and _internal_ipv6_prefix into their attribute reference respectively when they have dual stack support enabled upon creation.
Added field names are based on REST API reference and compute client protobuf:

Release Note Template for Downstream PRs (will be copied)

compute: added `internal_ipv6_range` to `data.google_compute_network` data source and `internal_ipv6_prefix` field to `data.google_compute_subnetwork` data source

Derived from GoogleCloudPlatform/magic-modules#9274

…rce reference attribute (hashicorp#9274)

Co-authored-by: Riley Karson <rileykarson@google.com>
[upstream:a01e0e02d240ec508cca38a52a97fbe9018f48bc]

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician merged commit 35f0774 into hashicorp:main Oct 16, 2023
2 checks passed
Copy link

I'm going to lock this pull request 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 related to this change, 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 Nov 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant