Merge lp:~jml/juju-jitsu/deploy-one into lp:juju-jitsu
Status: | Needs review |
---|---|
Proposed branch: | lp:~jml/juju-jitsu/deploy-one |
Merge into: | lp:juju-jitsu |
Diff against target: |
236 lines (+202/-1) 3 files modified
sub-commands/Makefile.am (+2/-0) sub-commands/deploy-one (+200/-0) sub-commands/deploy-to (+0/-1) |
To merge this branch: | bzr merge lp:~jml/juju-jitsu/deploy-one |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Clint Byrum (community) | Needs Fixing | ||
Review via email: mp+128061@code.launchpad.net |
Commit message
Add deploy-one subcommand. Deploys one instance of a service.
Description of the change
Hello!
A thing I do a lot when developing charms is this:
juju deploy $CHARM_NAME
jitsu watch $SERVICE_NAME --x-state pending --num-units 1
juju status
And then in another terminal:
juju debug-log
Because I was raised by humans, I've acquired their trait of being easily
bored by doing the same things over and over.
This branch adds a command that does pretty much all of that:
jitsu deploy-one --debug $CHARM_NAME
Combined with tools like 'alert' or <http://
takes much of the pain out of iterating on charms.
Known issues:
- Figuring out the default service name from the charm name is
somewhat kludgy.
- Always exits with 0, even if the charm did not deploy
cheers,
jml
Unmerged revisions
- 86. By Jonathan Lange
-
Fix a bunch of trivial syntax errors
- 85. By Jonathan Lange
-
Dicking about with documentation.
- 84. By Jonathan Lange
-
Add deploy-one to sub-commands.
- 83. By Jonathan Lange
-
More docs & sanity checking.
- 82. By Jonathan Lange
-
Dump status at the end.
- 81. By Jonathan Lange
-
Tidy up a little. Don't show debug log by default
- 80. By Jonathan Lange
-
First cut of deploy-one.
- 79. By Jonathan Lange
-
Flakes
Actually there is one issue, please fix. Add deploy-one to sub-commands/ Makefile. am