great to know that support for private container registries is being added. Awesome job guys!
Regarding the deployment of multicontainer applications:
Let’s assume that what I have now is something like this on my docker-compose.yml:
After pushing v0.2 of
service-2, I need to go into my docker-compose repo, change the image reference from
image: querty:0.1 to
image: querty:0.2, push to master, maintain this repo properly versioned, etc…
Instead, I think it would be nice to have something like this:
and then being able to update those environment variables on the application over the API, so that the CD pipeline could be streamlined in a way that doesn’t seem hacky.
On top of that, being able to issue requests over the API to restart/rebuild single services on the application (the equivalent of the
docker-compose up -d --build <service> command) would also be great. So that we don’t need to re-deploy all the services everytime we need to update a single service.