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

Maybe try something like this?
```}, new CustomResourceOptions { DependsOn = keyVault, IgnoreChanges = { "properties.value" } }); ```

docs seem to make it look like it has to be camelCase:
<https://www.pulumi.com/docs/intro/concepts/resources/options/ignorechanges/>

I found this that answered my question

<https://github.com/pulumi/pulumi-azure-native/issues/1280#issuecomment-964139979>

gotcha, so refresh before pulumi up and it’ll take your value. makes sense

Sorta - the second you make any changes to your resources in azure portal (or anywhere outside of code) the IngoreChanges flag doesnt work. It will only continue to ingorechanges for anything code via code.