(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling 2022-02-10T21:49:38+00:00 2022-02-10T21:49:38+00:00 Chris Lalos chris.lalos@gmail.com 2022-02-10T21:49:38+00:00 urn:sha1:600b870b399feb9e072748e07ea223556261fbe7 Handlers for per-boot/per-instance/per-once multipart MIME Add handlers for adding scripts to userdata that can be run at various frequencies. Scripts of type x-shellscript-per-boot, x-shellscript-per-instance, or x-shellscript-per-once can be added to a multipart MIME userdata message as part of instance userdata. These scripts will then be added to the appropriate per-boot, per-instance, or per-once directory in /var/lib/cloud/scripts/ during processing of userdata. 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-10-27T14:43:34+00:00 James Falcon james.falcon@canonical.com 2021-10-27T14:43:34+00:00 urn:sha1:1d01da5d9916d97ef463ba61a36b3f98f8911419 This commit removes automatically installing udev rules for hotplug and adds a module to install them instead. Automatically including the udev rules and checking if hotplug was enabled consumed too many resources in certain circumstances. Moving the rules to a module ensures we don't spend extra extra cycles on hotplug if hotplug functionality isn't desired. LP: #1946003 2021-09-01T14:23:55+00:00 Shreenidhi Shedi 53473811+sshedi@users.noreply.github.com 2021-09-01T14:23:55+00:00 urn:sha1:58c2de4c97de6cfa6edbf5319641f2ef71284895 Using flake8 inplace of pyflakes Renamed run-pyflakes -> run-flake8 Changed target name to flake8 in Makefile With pyflakes we can't suppress warnings/errors in few required places. flake8 is flexible in that regard. Hence using flake8 seems to be a better choice here. flake8 does the job of pep8 anyway. So, removed pep8 target from Makefile along with tools/run-pep8 script. Included setup.py in flake8 checks 2021-07-19T19:13:21+00:00 James Falcon therealfalcon@gmail.com 2021-07-19T19:13:21+00:00 urn:sha1:184c836a16e9954a2cba11ae21f07923077ec904 Adds a udev script which will invoke a hotplug hook script on all net add events. The script will write some udev arguments to a systemd FIFO socket (to ensure we have only instance of cloud-init running at a time), which is then read by a new service that calls a new 'cloud-init devel hotplug-hook' command to handle the new event. This hotplug-hook command will: - Fetch the pickled datsource - Verify that the hotplug event is supported/enabled - Update the metadata for the datasource - Ensure the hotplugged device exists within the datasource - Apply the config change on the datasource metadata - Bring up the new interface (or apply global network configuration) - Save the updated metadata back to the pickle cache Also scattered in some unrelated typing where helpful 2021-07-15T22:52:21+00:00 James Falcon therealfalcon@gmail.com 2021-07-15T22:52:21+00:00 urn:sha1:eacb0353803263934aa2ac827c37e461c87cb107 Python 3.6 added a new `policy` attribute to `MIMEMultipart`. MIMEMultipart may be part of the cached object pickle of a datasource. Upgrading from an old version of python to 3.6+ will cause the datasource to be invalid after pickle load. This commit uses the upgrade framework to attempt to access the mime message and fail early (thus discarding the cache) if we cannot. Commit 78e89b03 should fix this issue more generally. 2021-06-02T21:10:32+00:00 Robert Schweikert rjschwei@suse.com 2021-06-02T21:10:32+00:00 urn:sha1:29ac50f2b9e7634fc59fc161d77d27e970ae8080 Security scanners are often simple minded and complain on arbitrary settings such as file permissions. For /var/log/* having world read is one of these cases. 2021-05-13T17:55:41+00:00 James Falcon TheRealFalcon@users.noreply.github.com 2021-05-13T17:55:41+00:00 urn:sha1:864346999702e6b2b8bf7e6244a6608bcead72a5 Control is currently limited to boot events, though this should allow us to more easily incorporate HOTPLUG support. Disabling 'instance-first-boot' is not supported as we apply networking config too early in boot to have processed userdata (along with the fact that this would be a pretty big foot-gun). The concept of update events on datasource has been split into supported update events and default update events. Defaults will be used if there is no user-defined update events, but user-defined events won't be supplied if they aren't supported. When applying the networking config, we now check to see if the event is supported by the datasource as well as if it is enabled. Configuration looks like: updates: network: when: ['boot'] 2021-03-16T16:35:05+00:00 eb3095 45504889+eb3095@users.noreply.github.com 2021-03-16T16:35:05+00:00 urn:sha1:f35181fa970453ba6c7c14575b12185533391b97 The implementation in existing datasources means that vendordata_raw is not "raw" as it ideally would be. Instead, actual values may include bytes, string or list. If the value was a list, then the attempt to persist that data to a file in '_store_rawdata' would raise a TypeError. The change is to encode with util.json_dumps (which is safe for binary data) before writing. 2021-02-05T16:11:14+00:00 Andrew Bogott Andrewbogott@gmail.com 2021-02-05T16:11:14+00:00 urn:sha1:3cebe0df1e002bd85c8aa78e89f0ca507c17195a Add support for openstack's dynamic vendor data, which appears under openstack/latest/vendor_data2.json This adds vendor_data2 to all pathways; it should be a no-op for non-OpenStack providers. LP: #1841104