delta/cloud-init-git.git/cloudinit/cmd/tests/test_query.py, branch cla

query: do not handle non-decodable non-gzipped content (#543)

2020-08-24T16:13:52+00:00

cmd: cloud-init query to handle compressed userdata (#516)

2020-08-20T21:51:35+00:00

cloud-init query tries to directly load and decode
raw user-data from /var/lib/cloud/instance/user-data.txt.

This results in UnicodeDecodeErrors on some platforms which
provide compressed content.

Avoid UnicodeDecoderErrors when parsing compressed user-data at
/var/lib/cloud/instance/user-data.txt.

LP: #1889938

test: fix all flake8 E241 (#403)

2020-06-02T15:24:29+00:00

Remove extra spaces after a ','

cloudinit: replace "from six import X" imports (except in util.py) (#183)

2020-01-31T15:15:31+00:00

tests: mock uid when running as root (#113)

2019-12-16T15:08:25+00:00

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

query: better error when missing read permission on instance-data

2018-10-30T20:02:38+00:00

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

instance-data: fallback to instance-data.json if sensitive is absent.

2018-10-26T03:49:57+00:00

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

cli: add cloud-init query subcommand to query instance metadata

2018-09-25T21:59:16+00:00

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