nodepool/nodepool/cmd
Ian Wienand ddbcf1b07d Validate openstack provider pool labels have top-level labels
We broke nodepool configuration with
I3795fee1530045363e3f629f0793cbe6e95c23ca by not having the labels
defined in the OpenStack provider in the top-level label list.

The added check here would have found such a case.

The validate() function is reworked slightly; previously it would
return various exceptions from the tools it was calling (YAML,
voluptuous, etc.).  Now we have more testing (and I'd imagine we could
do even more, similar vaildations too) we'd have to keep adding
exception types.  Just make the function return a value; this also
makes sure the regular exit paths are taken from the caller in
nodepoolcmd.py, rather than dying with an exception at whatever point.

A unit test is added.

Co-Authored-By: Mohammed Naser <mnaser@vexxhost.com>
Change-Id: I5455f5d7eb07abea34c11a3026d630dee62f2185
2019-10-15 15:32:32 +11:00
..
__init__.py Fix version number when installing dev release 2019-05-08 14:18:37 -04:00
builder.py Add a dib-cmd option for diskimages 2019-08-22 10:09:00 +10:00
config_validator.py Validate openstack provider pool labels have top-level labels 2019-10-15 15:32:32 +11:00
launcher.py docker: don't daemonize when starting images 2019-02-08 20:53:04 +01:00
nodepoolcmd.py Validate openstack provider pool labels have top-level labels 2019-10-15 15:32:32 +11:00