| 2012-06-20 16:11:02 |
Jonathan Lange |
description |
When deploying a service, the 'juju deploy' command completes very quickly. However, the service isn't actually deployed at that time. If you want to do something _locally_ once the service is deployed, you have to run 'juju status' over and over until you can see that it's deployed. This wastes time and attention.
It would be great if there were some way of getting Juju to notify the user that the deploy had been finished. |
When deploying a service, the 'juju deploy' command completes very quickly. However, the service isn't actually deployed at that time. If you want to do something _locally_ once the service is deployed, you have to run 'juju status' over and over until you can see that it's deployed. This wastes time and attention.
This is particularly painful during charm development, as you do many, many deploys to test changes to a charm. Imagine having to poll to see if test run had completed?
It would be great if there were some way of getting Juju to notify the user that the deploy had been finished. |
|
