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

Compute Subnetwork secondary ip ranges drops note from upstream docs #2252

Open
VenelinMartinov opened this issue Jul 29, 2024 · 0 comments
Open
Labels
area/docs Improvements or additions to documentation kind/bug Some behavior is incorrect or out of spec

Comments

@VenelinMartinov
Copy link
Contributor

VenelinMartinov commented Jul 29, 2024

Describe what happened

The resource behaves a bit oddly when the parameters is omitted: #2251 due to pulumi/pulumi-terraform-bridge#2152

The upstream documentation calls this out: https://registry.terraform.io/providers/hashicorp/google/5.40.0/docs/resources/compute_subnetwork.html#secondary_ip_range

However, we've lost the note in ours leading to confusion with the resource: https://www.pulumi.com/registry/packages/gcp/api-docs/compute/subnetwork/#state_secondary_ip_ranges_python

Sample program

.

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

.

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@VenelinMartinov VenelinMartinov added area/docs Improvements or additions to documentation kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Jul 29, 2024
@VenelinMartinov VenelinMartinov removed the needs-triage Needs attention from the triage team label Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs Improvements or additions to documentation kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

No branches or pull requests

1 participant