Azure / Azure/container-apps-deploy-action
using imageToDeploy with a latest tag does not update revision
- Dominant language
- TypeScript
- Stars
- 94
- Forks
- 51
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 1
Description
I want to use this action to deploy "an already pushed application image".
In the CI/CD pipeline I create and push the image to the repository with the `latest` tag. However, when I specify the imageToDeploy parameter as: registry/image:latest everything works fine, however it will not create a new revision. The old revision stays online, until a new container is spinned up by a ACA scaling rule.
Is this a design choice? For now I am using specific version numbers as tags, which works. But I would like to be able to use a `latest` tag, which represents the currently running version.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.