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

No, <http://ghcr.io/{organization}/{package}:tag|ghcr.io/{organization}/{package}:tag> [stable]

<https://docs.aws.amazon.com/cli/latest/reference/ecs/update-service.html>

```If your updated Docker image uses the same tag as what is in the existing task definition for your service (for example, my_image:latest ), you don't need to create a new revision of your task definition. You can update the service using the forceNewDeployment option. The new tasks launched by the deployment pull the current image/tag combination from your repository when they start.```

<@U043TNJT17H> that’s only applicable if you’re doing imperative actions. Pulumi is declarative, and as far as Pulumi is concerned, nothing has changed

i see, so the best solution would be fetch latest digest of docker image and set as containerImage?

pulumi has any adaption for working with ghcr packages?