(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.1 2020-01-31T15:15:31+00:00 2020-01-31T15:15:31+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-01-31T15:15:31+00:00 urn:sha1:1bb1896ec900622e02c1ffb59db4d3f2df4a964d 2019-12-16T15:08:25+00:00 Joshua Powers josh.powers@canonical.com 2019-12-16T15:08:25+00:00 urn:sha1:22054368db4cb83074860f8114e61a8fb183489d The query command checks the user's uid when running and takes two different code paths. As a normal user is returns fake data, that these tests were expecting. As a root user, the actual user and vendor data files are ready. LP: #1856096 2019-10-24T20:02:15+00:00 Scott Moser smoser@brickies.net 2019-10-24T20:02:15+00:00 urn:sha1:5bec6b0e2a2ce5fd03bb04f441536fc130e67997 Here we replace uses of the pyyaml module directly with functions provided by cloudinit.safeyaml. Also, change/move cloudinit.util.yaml_dumps to cloudinit.safeyaml.dumps LP: #1849640 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-10-30T20:02:38+00:00 Chad Smith chad.smith@canonical.com 2018-10-30T20:02:38+00:00 urn:sha1:d74d3f0ff5c8d453f626b113f4e6065322f822fa Emit a permissions error instead of "Missing instance-data.json" when non-root user doesn't have read-permission on /run/cloud-init/instance-data.json 2018-10-26T03:49:57+00:00 Chad Smith chad.smith@canonical.com 2018-10-26T03:49:57+00:00 urn:sha1:dc0be9c56f78537f1808934d26f5aa0868ae7842 On cloud-init upgrade path from 18.3 to 18.4 cloud-init changed how instance-data is written. Cloud-init changes instance-data.json from root read-only to redacted world-readable content, and provided a separate unredacted instance-data-sensitive.json which is read-only root. Since instance-data is only rewritten from cache on reboot, the query and render tools needed fallback to use the 'old' instance-data.json if the new sensitive file isn't yet present. This avoids error messages from tools about an absebt /run/instance-data-sensitive.json file. LP: #1798189 2018-10-09T22:19:20+00:00 Chad Smith chad.smith@canonical.com 2018-10-09T22:19:20+00:00 urn:sha1:6ee8a2c557ccdc8be54bcf8a8762800c10f3ef49 Add a quick cloud lookup utility in order to more easily determine the cloud on which an instance is running. The utility parses standardized attributes from /run/cloud-init/instance-data.json to print the canonical cloud-id for the instance. It uses known region maps if necessary to determine on which specific cloud the instance is running. Examples: aws, aws-gov, aws-china, rackspace, azure-china, lxd, openstack, unknown 2018-09-25T21:59:16+00:00 Chad Smith chad.smith@canonical.com 2018-09-25T21:59:16+00:00 urn:sha1:fc4b966ba928b30b1c586407e752e0b51b1031e8 Cloud-init caches any cloud metadata crawled during boot in the file /run/cloud-init/instance-data.json. Cloud-init also standardizes some of that metadata across all clouds. The command 'cloud-init query' surfaces a simple CLI to query or format any cached instance metadata so that scripts or end-users do not have to write tools to crawl metadata themselves. Since 'cloud-init query' is runnable by non-root users, redact any sensitive data from instance-data.json and provide a root-readable unredacted instance-data-sensitive.json. Datasources can now define a sensitive_metadata_keys tuple which will redact any matching keys which could contain passwords or credentials from instance-data.json. Also add the following standardized 'v1' instance-data.json keys:   - user_data: The base64encoded user-data provided at instance launch   - vendor_data: Any vendor_data provided to the instance at launch   - underscore_delimited versions of existing hyphenated keys:     instance_id, local_hostname, availability_zone, cloud_name 2018-09-17T13:07:39+00:00 Robert Schweikert rjschwei@suse.com 2018-09-17T13:07:39+00:00 urn:sha1:c714651c1988a17f457426de63cdb8514d5a81b4 If the user has removed the default configuration file or does not set the syslog_fix_perms config option the user still ends up with a warning on SUSE distributions. Add root:root to the default builtin config.