No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

try this <https://www.pulumi.com/docs/concepts/options/ignorechanges/>

<@U060XTPL0RH> ya, I'm aware of the resource option, I just don't know how to "select" the resources I care about.

so, like select a resource by name, apiVersion, kind, namespace, etc, and then ignore a specific field within it

yeah so it probably selectable in json or yaml format. look at how it is organized in the state file.

oh, that's a good idea! I didn't think to look at the state file

is there a way to do specify an ignoreChanges like a transformation? (make it dynamic)

the only thing I can think of right now is do some preprocessing of the yaml before passing it (and the ignoreChanges array) to the `ConfigGroup` resource

idk but you could try <https://www.pulumi.com/ai>

like, unmarshal all the resources into `[]map[string]any` so I can see what's inside, and dynamically construct the `ignoreChanges` array from that.

You should be able to use transformations for this. Setting up an example now

oh, there's an example of modifying resource options on the docs. You can substitute `Alias` for `IgnoreChanges`.
<https://www.pulumi.com/registry/packages/kubernetes/api-docs/yaml/configgroup/#yaml-with-transformations>

because the ConfigGroup produces the other resources, using a transformation allows me to inject other resourceOptions, such as `ignoreChanges` into specific resources.

I'll try this out and see if I run into any problems

```// Set a resource alias for a previous name.
func(state map[string]interface{}, opts ...pulumi.ResourceOption) {
	if state["kind"] == "Deployment" {
		aliases := pulumi.Aliases([]pulumi.Alias{
			{
				Name: pulumi.String("oldName"),
			},
		})
		opts = append(opts, aliases)
	}
},```
uh... this shouldn't work... `opts` isn't a pointer.. this append operation would remain local to the this transformation function (it would not be visible to the code that calls this transformation)

maps are pointers though, so it makes sense that changes to a map _will_ be seen from outside the transformation function (after the transformation runs).

I think you're right, and this is a limitation in the go-sdk version of the provider.
It's worth updating your issue into a feature request

well... I think this is more of a bug than a feature request