Merge lp:~harlowja/cloud-init/cloud-init-dynamic-distro-check into lp:~cloud-init-dev/cloud-init/trunk
| Status: | Rejected |
|---|---|
| Rejected by: | Scott Moser on 2017-06-06 |
| Proposed branch: | lp:~harlowja/cloud-init/cloud-init-dynamic-distro-check |
| Merge into: | lp:~cloud-init-dev/cloud-init/trunk |
| Diff against target: |
115 lines (+62/-16) 2 files modified
cloudinit/exceptions.py (+28/-0) cloudinit/stages.py (+34/-16) |
| To merge this branch: | bzr merge lp:~harlowja/cloud-init/cloud-init-dynamic-distro-check |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Server Team CI bot | continuous-integration | Needs Fixing on 2016-07-22 | |
| cloud-init commiters | 2016-07-21 | Pending | |
|
Review via email:
|
|||
- 1260. By Joshua Harlow on 2016-07-21
-
Use a more advanced module 'working' function
that by default performs the same distro checking
behavior (but allows modules to provide there
own if they so desire to).
| Joshua Harlow (harlowja) wrote : | # |
- 1261. By Joshua Harlow on 2016-07-22
-
Rearrange some of the pre_handling code.
FAILED: Continuous integration, rev:1261
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
https:/
Executed test runs:
None: https:/
Click here to trigger a rebuild:
https:/
| Scott Moser (smoser) wrote : | # |
Hello,
Thank you for taking the time to contribute to cloud-init. Cloud-init has moved its revision control system to git. As a result, we are marking all bzr merge proposals as 'rejected'. If you would like to re-submit this proposal for review, please do so by following the current HACKING documentation at http://
Unmerged revisions
- 1261. By Joshua Harlow on 2016-07-22
-
Rearrange some of the pre_handling code.
- 1260. By Joshua Harlow on 2016-07-21
-
Use a more advanced module 'working' function
that by default performs the same distro checking
behavior (but allows modules to provide there
own if they so desire to). - 1259. By Joshua Harlow on 2016-07-21
-
Allow modules to provide a 'is_usable_on' function
This function, if it exists will allow for the module
to decide if it works on the running distro, making it
a little more flexible (vs the previous distro lists that
are more static) so that the module can itself figure out
if it should be operational or not.


Yup, I updated it to try that approach instead; seems like its better IMHO.