03/13/2023, 7:17 PM
i have a handful of resources that i have set up to ignore changes for certain properties. these are GCP resources where labels change behind the scenes and they're beyond my control. these ignored changes have worked fine up until recently, where some of these properties appear in diffs when i do
pulumi up
, despite having been ignored. does anyone know why this might be happening?
here's an example, i have a cloud run resource that's showing this diff:
~ template: {
          ~ metadata: {
              ~ annotations: {
                  - <|>: "421.0.0"
but i have this defined in the IgnoreChanges array:
seems like this could be my issue