Merge ~smoser/cloud-init:feature/integration-execute-with-string into cloud-init:master
| Status: | Rejected |
|---|---|
| Rejected by: | Scott Moser on 2017-09-13 |
| Proposed branch: | ~smoser/cloud-init:feature/integration-execute-with-string |
| Merge into: | cloud-init:master |
| Diff against target: |
46 lines (+8/-2) 2 files modified
tests/cloud_tests/instances/base.py (+2/-1) tests/cloud_tests/instances/lxd.py (+6/-1) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Server Team CI bot | continuous-integration | Needs Fixing on 2017-09-08 | |
| Joshua Powers (community) | Approve on 2017-09-08 | ||
| cloud-init commiters | 2017-09-08 | Pending | |
|
Review via email:
|
|||
Commit Message
tests: execute: support command as a string, change default env parm.
If a string is passed to execute, then invoke 'sh', '-c', 'string'.
That allows the less verbose execution of simple commands:
image.execute("ls /run")
compared to the more explicit but longer winded:
image.
If 'env' was ever modified in execute or a method that it called,
then the next invocation's default value would be changed. Instead
use None and then set to a new empty dict in the method.
FAILED: Continuous integration, rev:bfcb2912338
https:/
Executed test runs:
SUCCESS: Checkout
FAILED: Unit & Style Tests
Click here to trigger a rebuild:
https:/
| Scott Moser (smoser) wrote : | # |
rejected, this was largely pulled into
https:/
Unmerged commits
- bfcb291... by Scott Moser on 2017-09-08


+1 thanks for this it makes it a lot easier on simple commands.