Merge lp:~harlowja/cloud-init/write-files-fetch-from-somewhere into lp:~cloud-init-dev/cloud-init/trunk
Proposed by
Joshua Harlow
Status: | Rejected |
---|---|
Rejected by: | Scott Moser |
Proposed branch: | lp:~harlowja/cloud-init/write-files-fetch-from-somewhere |
Merge into: | lp:~cloud-init-dev/cloud-init/trunk |
Diff against target: |
218 lines (+132/-9) 3 files modified
cloudinit/config/cc_write_files.py (+27/-3) cloudinit/url_helper.py (+20/-6) tests/unittests/test_handler/test_handler_write_files.py (+85/-0) |
To merge this branch: | bzr merge lp:~harlowja/cloud-init/write-files-fetch-from-somewhere |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Server Team CI bot | continuous-integration | Needs Fixing | |
Scott Moser | Needs Fixing | ||
Review via email: mp+254816@code.launchpad.net |
To post a comment you must log in.
Unmerged revisions
- 1095. By Joshua Harlow
-
Fixs log entry/output
- 1094. By Joshua Harlow
-
Avoid fetching automagically and add test for this
- 1093. By Joshua Harlow
-
Some contents/text tweaks and handler tests
- 1092. By Joshua Harlow
-
Only do the decoding on py3.x
- 1091. By Joshua Harlow
-
Fix reading of files for py3.x
util.read_
file_or_ url needs to have a __str__ that
returns the right type for py3.x; so make sure that if
binary data is read that it is decoded. - 1090. By Joshua Harlow
-
Fix extra space
- 1089. By Joshua Harlow
-
Allow write_files to fetch content
Instead of requring write_files to be always provided
all the data (which can be big/large blobs); allow it to
fetch that data from either a local file or a http/https
url instead (saving precious user-data space).
I think better to require user to be explicit that this is a remote file. '.
I don't like the interpretation of content. The problem being, if it seems quite likely that some config file that someone would want to 'write-files' of might start with 'http://
If they try to send such a content, then cloud-init would interpret that content and pull the url.
So, in short, I'd rather: www.yahoo. com of-cloud- init-for- copy /usr/bin/ true old-write_ files
write_files:
- path: /myfile-from-remote
content_url: http://
- path: /odd-use-
content_url: file://
- path: /myfile-
content: "Hi Mom"
Than: www.yahoo. com
write_files:
- path: /myfile-from-remote
content: http://
in the event of an entry having both 'content_url' and 'content', I guess I'd warn and use the 'content' field.
Agree/ disagree?