lp://staging/~harlowja/cloud-init/write-files-fetch-from-somewhere

Branch merges

Propose for merging

No branches dependent on this one.

Rejected for merging into lp://staging/~cloud-init-dev/cloud-init/trunk

Server Team CI bot: Needs Fixing (continuous-integration) on 2016-07-22

Scott Moser: Needs Fixing on 2015-04-01

Diff: 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)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1095. By Joshua Harlow on 2015-04-07

Fixs log entry/output

1094. By Joshua Harlow on 2015-04-07

Avoid fetching automagically and add test for this

1093. By Joshua Harlow on 2015-03-31

Some contents/text tweaks and handler tests

1092. By Joshua Harlow on 2015-03-31

Only do the decoding on py3.x

1091. By Joshua Harlow on 2015-03-31

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 on 2015-03-31

Fix extra space

1089. By Joshua Harlow on 2015-03-31

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).

1088. By Scott Moser on 2015-03-31

adjust cc_snappy for snappy install package with config.

It was believed that to install a package with config the command was:
  snappy install --config=config-file <package>
Instead, what was implemented in snappy was:
  snappy install <package> [<config-file>]

This modifies cloud-init to invoke the latter and changes the tests
appropriately.

1087. By Scott Moser on 2015-03-27

fix snappy package installation.

Some tests added here to make sure this works.
The install '--config' will only start to work with the next
version of snappy-go.

1086. By Scott Moser on 2015-03-27

NoCloud: the local portion of NoCloud incorrectly claimed datasources

The intent has always been for the local datasource (NoCloud) to require
the provider of metadata to provide 'dsmode=local'. If that wasn't found,
then the default 'dsmode' would be 'net', and the NoCloudNet datasource
would then find the data.

The bug here was that the default 'net' wasn't being set when
data was found on a local source.