Hi all! New to pulumi, though I've got a fair amo...
# aws
w
Hi all! New to pulumi, though I've got a fair amount of background with terraform so I get the concepts, if not the implementation specifics yet. 🙂 I'm generally working with inherited code, though I've been doing some basic changes in a dev environment to get familiar, creating instances and that sort of thing, which is fine. However, I just started getting some updates showing in the list when I go to do a preview/up/refresh, specifically to two lambdas. I haven't made changes to them, but even more strangely - while it's saying there's an update, it's not actually showing anything as changing. I did see a convo earlier about this, so I tried what they did, which was adding
ignoreChanges: [*]
, but unlike that earlier thread mine is still exhibiting the same behaviour afterwards. I do see specific changes indicated in the output when I actually add/change other resources, so I'm not sure what's going on in this one strange case, or how to dig in further.
Oh, just found something interesting. Originally, we'd had
ignoreChanges: ["imageUri"]
on these, which I changed to the
*
for that test above. However, for fun, I tried changing a different parameter on one of the two lambdas in question, and then the output shows me a change to the imageUri field. (Which is not surprising, because we've deployed updates to these two via a separate deploy process, hence the ignore flag.)
(to be a bit more specific, in a pipeline we have updates to the lambda code creating a new image version in ECR, and tagging it to a particular tag (not latest, but same idea). And in the pulumi code, we just have the repo+tag as the imageUri. So neither of those things have changed, but the underlying image name that the tag points to has.)