This message was deleted.

sparse-intern-71089

10/16/2022, 1:48 AM

This message was deleted.

echoing-dinner-19531

10/16/2022, 9:57 AM

Has

containerImage

changed?

clean-oil-72875

10/16/2022, 1:25 PM

No, ghcr.io/{organization}/{package}:tag [stable]

clean-oil-72875

10/16/2022, 1:35 PM

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

Copy code

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.

billowy-army-68599

10/16/2022, 2:36 PM

@clean-oil-72875 that’s only applicable if you’re doing imperative actions. Pulumi is declarative, and as far as Pulumi is concerned, nothing has changed

clean-oil-72875

10/16/2022, 2:38 PM

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

billowy-army-68599

10/16/2022, 2:40 PM

yes exactly

🙌 1

clean-oil-72875

10/16/2022, 2:41 PM

pulumi has any adaption for working with ghcr packages?

billowy-army-68599

10/16/2022, 5:17 PM

what do you need exactly?

11 Views

Open in Slack

Previous Next

Pulumi Community

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.