~chad.smith/cloud-init:cleanup/schema-annotate-invalid-yaml

Last commit made on 2018-05-21
Get this branch:
git clone -b cleanup/schema-annotate-invalid-yaml https://git.launchpad.net/~chad.smith/cloud-init
Only Chad Smith can upload to this branch. If you are Chad Smith please log in for upload directions.

Branch merges

Branch information

Name:
cleanup/schema-annotate-invalid-yaml
Repository:
lp:~chad.smith/cloud-init

Recent commits

142f143... by Chad Smith

rename unit test per lint error

7706458... by Chad Smith

fix unit test. py3 str(str) reports class instead of type

0701568... by Chad Smith

exit non-zero and print error when config-file is absent

51169e6... by Chad Smith

lints and style checks. No longer report full tracebacks for yaml load errors, instead log a warning with the error details. Unit test coverage for util.load_yaml parse errors

dc5a0ba... by Chad Smith

annotate on yaml parse errors

12eafdf... by Chad Smith

tests: update-ca-certificates on bionic gens less links

14af1f0... by Chad Smith

annotate on yaml parse errors

30e730f... by Scott Moser

read_file_or_url: move to url_helper, fix bug in its FileResponse.

The result of a read_file_or_url on a file and on a url would differ
in behavior.
  str(UrlResponse) would return UrlResponse.contents.decode('utf-8')
while
  str(FileResponse) would return str(FileResponse.contents)

The difference being "b'foo'" versus "foo".

As part of the general goal of cleaning util, move read_file_or_url
into url_helper.

2dab704... by Ryan Harper

cloud_tests: help pylint

pylint missed finding a typo in the lxd platform because it could not
determine that the variable was being used was a string. The variable
was set by loading a yaml file which pylint couldn't know that it
would be a string. In these cases, we can be more explicit.

13f7f4e... by Scott Moser

flake8: fix flake8 errors in previous commit.