Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes lp:1596858 and refactors the deploy command #6144

Merged
merged 1 commit into from
Sep 8, 2016

Conversation

kat-co
Copy link
Contributor

@kat-co kat-co commented Sep 2, 2016

This work builds on previous work to refactor the deploy command to take
in an API interface instead of instantiating clients throughout. This
brings us closer to achieving that goal and allows us to write unit
tests for the majority of the deploy command (majority of the current
tests are so-called "full-stack").

The highlights of this patch are:

  • Modifies the output when deploying bundles to the format suggested in
    the bug. The details can still be achieved by passing the --debug
    flag to the command.
  • Removed redundant checks for format of output when deploying
    bundles. This check is done in a single test and need not be
    replicated everywhere.
  • Introduced a type, callMocker to assist with mocking interfaces for
    tets. This can be found in deploy_test.go. In the long run, it would
    be nice for this type to move over to juju/testing to live with the
    Stub class.

(Review request: http://reviews.vapour.ws/r/5582/)

@kat-co kat-co force-pushed the fix-1596858-bundle-deploy-msg branch 3 times, most recently from 8711bf1 to 646af4f Compare September 3, 2016 01:29
@kat-co kat-co changed the title WIP: Fix 1596858 bundle deploy msg Fixes lp:1596858 and refactors the deploy command Sep 3, 2016
This work builds on previous work to refactor the deploy command to take
in an API interface instead of instantiating clients throughout. This
brings us closer to achieving that goal and allows us to write unit
tests for the majority of the deploy command (majority of the current
tests are so-called "full-stack").

The highlights of this patch are:

- Modifies the output when deploying bundles to the format suggested in
  the bug. The details can still be achieved by passing the `--debug`
  flag to the command.

- Removed redundant checks for format of output when deploying
  bundles. This check is done in a single test and need not be
  replicated everywhere.

- Introduced a type, `callMocker` to assist with mocking interfaces for
  tets. This can be found in deploy_test.go. In the long run, it would
  be nice for this type to move over to juju/testing to live with the
  `Stub` class.
@kat-co kat-co force-pushed the fix-1596858-bundle-deploy-msg branch from 646af4f to 1a4a96c Compare September 6, 2016 14:07
@kat-co
Copy link
Contributor Author

kat-co commented Sep 8, 2016

$$merge$$

@jujubot
Copy link
Collaborator

jujubot commented Sep 8, 2016

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju

@jujubot jujubot merged commit 271976e into juju:master Sep 8, 2016
@kat-co kat-co deleted the fix-1596858-bundle-deploy-msg branch October 4, 2016 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants