(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=circinus-public-unmaintained 2021-12-16T02:16:38+00:00 2021-12-16T02:16:38+00:00 James Falcon james.falcon@canonical.com 2021-12-16T02:16:38+00:00 urn:sha1:bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf Applied Black and isort, fixed any linting issues, updated tox.ini and CI. 2021-12-06T22:27:12+00:00 Brett Holman bholman.devel@gmail.com 2021-12-06T22:27:12+00:00 urn:sha1:bedac77e9348e7a54c0ec364fb61df90cd893972 Improve schema validation. This adds strict validation of config module definitions at testing time, with plumbing included for future runtime validation. This eliminates a class of bugs resulting from schemas that have definitions that are incorrect, but get interpreted by jsonschema as "additionalProperties" that are therefore ignored. - Add strict meta-schema for jsonschema unit test validation - Separate schema from module metadata structure - Improve type annotations for various functions and data types Cleanup: - Remove unused jsonschema "required" elements - Eliminate manual memoization in schema.py:get_schema(), reference module.__doc__ directly 2020-06-08T16:49:12+00:00 Scott Moser smoser@brickies.net 2020-06-08T16:49:12+00:00 urn:sha1:3c551f6ebc12f7729a2755c89b19b9000e27cc88 This was painful, but it finishes a TODO from cloudinit/subp.py. It moves the following from util to subp: ProcessExecutionError subp which target_path I moved subp_blob_in_tempfile into cc_chef, which is its only caller. That saved us from having to deal with it using write_file and temp_utils from subp (which does not import any cloudinit things now). It is arguable that 'target_path' could be moved to a 'path_utils' or something, but in order to use it from subp and also from utils, we had to get it out of utils. 2019-03-04T22:36:07+00:00 Daniel Watkins daniel.watkins@canonical.com 2019-03-04T22:36:07+00:00 urn:sha1:109772c2e9066f5ae53aa2806c4bb4a2ab6f4bff Previously, init.paths.cloud_dir has a trailing slash, which meant that "/var/lib/cloud//seed" was being compared to "/var/lib/cloud/seed" and (of course), never matching. In this commit, switch to using os.path.join to avoid this case (and update the tests to catch it in future). LP: #1818571 2019-01-31T03:52:13+00:00 Chad Smith chad.smith@canonical.com 2019-01-31T03:52:13+00:00 urn:sha1:489553547f3461bd8ff67d3099237694130eb714 Avoid traceback when cloud-init clean is run from within /var/lib/cloud/ deleted dirs. LP: #1795508 2018-01-03T19:56:22+00:00 Chad Smith chad.smith@canonical.com 2018-01-03T19:56:22+00:00 urn:sha1:0b5bacb1761aefa74adb79bd1683d614bdf8c998 Fix cloud-init clean subcommand to unlink symlinks instead of calling del_dir. LP: #1741093 2017-12-05T23:25:11+00:00 Chad Smith chad.smith@canonical.com 2017-12-05T23:25:11+00:00 urn:sha1:30b4d15764a1a9644379cf95770e8b2480856882 The 'cloud-init clean' command allows a user or script to clear cloud-init artifacts from the system so that cloud-init sees the system as unconfigured upon reboot. Optional parameters can be provided to remove cloud-init logs and reboot after clean. The 'cloud-init status' command allows the user or script to check whether cloud-init has finished all configuration stages and whether errors occurred. An optional --wait argument will poll on a 0.25 second interval until cloud-init configuration is complete. The benefit here is scripts can block on cloud-init completion before performing post-config tasks.