You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ignore_changes not working with the gcp.compute.NetworkEndpointGroup.get function
Sample program
Create a NEG with pulumi. And connect it to the related backend pod services.
Make changes in NEG without pulumi.
Try to get the NEG with pulumi.
Ignore changes will not work and it will detect all changes anyway.
import pulumi_gcp as gcp
gcp.compute.NetworkEndpointGroup.get(resource_name=internal_neg_name, id=internal_neg_id,
opts=pulumi.ResourceOptions(ignore_changes=["*"])
Log output
No response
Affected Resource(s)
gcp.compute.NetworkEndpointGroup.get
Output of pulumi about
CLI
Version 3.136.1
Go Version go1.23.2
Go Compiler gc
Plugins
KIND NAME VERSION
resource docker 4.5.5
resource gcp 7.38.0
resource kubernetes 4.17.1
resource postgresql 3.11.3
language python 3.136.1
resource random 4.16.4
Host
OS darwin
Version 14.5
Arch x86_64
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).
The text was updated successfully, but these errors were encountered:
Unfortunately, the way ignore changes works is that it only effects the inputs to a resource, not the outputs: https://www.pulumi.com/docs/iac/concepts/options/ignorechanges/ In your case, for .get methods, the changes are only to the outputs, so these can not be ignored by ignoreChanges.
What are you trying to achieve here? What changes are you trying to ignore and why are they impacting your program?
Describe what happened
The
ignore_changes
not working with thegcp.compute.NetworkEndpointGroup.get
functionSample program
Log output
No response
Affected Resource(s)
gcp.compute.NetworkEndpointGroup.get
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).
The text was updated successfully, but these errors were encountered: