Module configuration validation

Bug #1079386 reported by Joshua Harlow
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Expired
Low
Unassigned

Bug Description

It would be nice if modules could say validate the configuration they will be pulling from yaml before using it.

Say a module needs a configuration with an list in it (for whatever usage) and strings in that list. It'd be nice to have a pre-module stage or have the modules use some external library to validate that there expected/desired/known input is correct. This would make it so that the yaml that is documented is verified and situations where a module expects a list + stirngs in that list but say that list has dictionaries (or other types) in it are invalid before the module actually runs.

Right now alot of those kind of checks don't exist (some do though...)

Related branches

Scott Moser (smoser)
Changed in cloud-init:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
James Falcon (falcojr) wrote :
Changed in cloud-init:
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.