Merge lp:~jtv/maas/bug-1238376 into lp:~maas-committers/maas/trunk
Status: | Merged |
---|---|
Approved by: | Jeroen T. Vermeulen |
Approved revision: | no longer in the source branch. |
Merged at revision: | 1701 |
Proposed branch: | lp:~jtv/maas/bug-1238376 |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
243 lines (+51/-109) 5 files modified
etc/maas/import_ephemerals (+14/-0) etc/maas/pserv.yaml (+26/-3) setup.py (+1/-0) src/provisioningserver/import_images/ephemerals_script.py (+1/-24) src/provisioningserver/import_images/tests/test_ephemerals_script.py (+9/-82) |
To merge this branch: | bzr merge lp:~jtv/maas/bug-1238376 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gavin Panella (community) | Approve | ||
Review via email: mp+190656@code.launchpad.net |
Commit message
Keep the legacy ephemerals import script config for now.
Description of the change
This took a while to run through its paces. As per bug 1238376, users are bemused with the import_pxe_files config no longer being included as configuration for the ephemerals import script. Therefore in this branch I change it as follows:
1. No longer rewrite pserv.yaml with the combined config, and no longer move the import_ephemerals config out of the way. I kept the generic infrastructure for doing these things, but not the specific code.
2. Strip the now-inert items out of the import_ephemerals config, and add a notice about the file being obsolete. This means that upgrading users will get a notice about the change, giving them a fair chance of learning about the change. And it means that any further changes they make to either import_pxe_files or import_ephemerals will still be respected.
3. Document the new options in pserv.yaml. These options will still be respected, unless the legacy shell scripts set different values. It'd be nice to have this the other way around, but the config has no real difference between letting a setting empty to use the default, and deliberately setting it to its default value. At least with the legacy config we can tell whether a value has been set or not.
A packaging branch will follow, to add the new /etc/maas/
Jeroen
Sad, but probably the right thing to do. Undoing badness takes time, and this is proof.