I'm not sure what I think about this. I like that it will now catch errors that were previously swallowed... I ran into this when I added some schema changes and failed to add skipUnlessJsonSchema and there were no failures... it wasnt skipped and there were no failures, just passed as the import error was ignored.
So I like that. What I do not like is that in reality since we support running without jsonschema, cloud-init can never actually *use* strict=True. hm.. Thoughts? -- https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/343610 Your team cloud-init commiters is requested to review the proposed merge of ~smoser/cloud-init:cleanup/schema-raise-import-error-if-validate-strict into cloud-init:master. _______________________________________________ Mailing list: https://launchpad.net/~cloud-init-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~cloud-init-dev More help : https://help.launchpad.net/ListHelp
