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

Morning all - I have (potentially) a basic question around how we're using pulumi to push images to an ACR...

• we have used Pulumi to build our ACR in Azure
• we have also used Pulumi to create an Azure Container App which will use an image pushed to the ACR
• we use Pulumi to create a `new Image()` and set the image name as: &lt;name&gt;.<http://azurecr.io/|azurecr.io/>&lt;appname&gt;:&lt;tag&gt;
• the &lt;tag&gt; is set to the name of a branch that is being worked on (so that there could be multiple images in teh ACR which map to different branches).  A main branch to set the tag to `latest`.
• however, when we do a pulumi up - the delta means that any images in the ACR gets deleted if it does not match the branch/tag that is being pushed which means we cannot have multiple engineers (and/or branches) being worked on and pushing to the ACR without the other one being removed
• we would also like to keep images around incase of needing to rollback


Could anyone recommend a way in which to get Pulumi not to remove images on subsequent deploys?

Anyone in <#CRVK66N5U|> able to help with this one?

Maybe the "ignoreChanges" resource option can help you out here?

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