Add apiv4 bundle id support to deploy-target #695
Conversation
To QA
|
Test FAILed. |
Spurious failure, running manually. |
👍 QA okay - works like a dream, tried a few different bundles. |
Passed when ran manually http://ci.jujugui.org:8080/job/juju-gui/2373/ |
deploying a bundle via the deployer. | ||
|
||
@method getBundleYAML | ||
@param {String} id Bundle id in apiv4 format. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might make it clear we're talking charmstore here, e.g. ... id in v4 charmstore api format
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea
👍 @hatched, thanks for the explanations. |
Thanks for the reviews! |
Status: merge request accepted. Url: http://ci.jujugui.org:8080/job/juju-gui-merge |
Add apiv4 bundle id support to deploy-target The jujucharms.com website allows users to "add to demo" bundles to play around with. It has had to guess at the apiv3 bundle id for some time now which has caused a number of bugs. This adds apiv4 bundle support to the GUI's deploy-target handler so that jujucharms.com can now use the apiv4 bundle id's.
The jujucharms.com website allows users to "add to demo" bundles to play around with. It has had to guess at the apiv3 bundle id for some time now which has caused a number of bugs. This adds apiv4 bundle support to the GUI's deploy-target handler so that jujucharms.com can now use the apiv4 bundle id's.