Merge ppa-dev-tools:set-command into ppa-dev-tools:main
Status: | Merged |
---|---|
Merge reported by: | Bryce Harrington |
Merged at revision: | b6866c83422f9c1d55beea458a454211b50e3a23 |
Proposed branch: | ppa-dev-tools:set-command |
Merge into: | ppa-dev-tools:main |
Diff against target: |
281 lines (+143/-15) 3 files modified
scripts/ppa (+89/-3) tests/helpers.py (+16/-0) tests/test_scripts_ppa.py (+38/-12) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Athos Ribeiro (community) | Approve | ||
Canonical Server Core Reviewers | Pending | ||
Canonical Server Reporter | Pending | ||
Review via email: mp+434685@code.staging.launchpad.net |
Description of the change
This is the first piece of a batch of commits for implementing the 'ppa set' command. This first MP just provides three super basic settings, that are already supported by the 'ppa create' command, and generalizes the code so it can be reused for both set and create.
This is one of those situations where the functionality itself was simple to implement, and all the real work was in crafting the test cases. So part of the reason for sending this one initial commit by itself is to get feedback on the testing approach in isolation from all the other settings.
There was an error fetching revisions from git servers. Please try again in a few minutes. If the problem persists, contact Launchpad support.
Thanks, Bryce!
The commit message has a duplication in "... the same set of of configuration...".
I also left a couple minor comments inline regarding duplication of value testing, but those should not be blockers.
LGTM.