-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
validate reservation.yaml #174
Comments
Like the idea. Implementing the Instead of a @ivotron, @BeyondTheClouds/enos what do you think? In a second time we could implement a better cli, à la |
Let's start hacking this ;) |
'enos new' takes a new argument called '--provider' with the name of one of enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm, chameleonbaremetal, openstack, vmong5k, static). It then generates a reservation.yaml specific to that provider. This and the json schema validation from enoslib implement BeyondTheClouds#174.
'enos new' takes a new argument called '--provider' with the name of one of enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm, chameleonbaremetal, openstack, vmong5k, static). It then generates a reservation.yaml specific to that provider. This and the json schema validation from enoslib implement BeyondTheClouds#174.
'enos new' takes a new argument called '--provider' with the name of one of enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm, chameleonbaremetal, openstack, vmong5k, static). It then generates a reservation.yaml specific to that provider. This and the json schema validation from enoslib implement BeyondTheClouds#174.
'enos new' takes a new argument called '--provider' with the name of one of enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm, chameleonbaremetal, openstack, vmong5k, static). It then generates a reservation.yaml specific to that provider. This and the json schema validation from enoslib implement BeyondTheClouds#174.
'enos new' takes a new argument called '--provider' with the name of one of enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm, chameleonbaremetal, openstack, vmong5k, static). It then generates a reservation.yaml specific to that provider. This and the json schema validation from enoslib implement BeyondTheClouds#174.
'enos new' takes a new argument called '--provider' with the name of one of enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm, chameleonbaremetal, openstack, vmong5k, static). It then generates a reservation.yaml specific to that provider. This and the json schema validation from enoslib implement BeyondTheClouds#174,BeyondTheClouds#315
'enos new' takes a new argument called '--provider' with the name of one of enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm, chameleonbaremetal, openstack, vmong5k, static). It then generates a reservation.yaml specific to that provider. This and the json schema validation from enoslib implement BeyondTheClouds#174 and implement BeyondTheClouds#315
'enos new' takes a new argument called '--provider' with the name of one of enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm, chameleonbaremetal, openstack, vmong5k, static). It then generates a reservation.yaml specific to that provider. This and the json schema validation from enoslib implement BeyondTheClouds#174 and implement BeyondTheClouds#315
'enos new' takes a new argument called '--provider' with the name of one of enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm, chameleonbaremetal, openstack, vmong5k, static). It then generates a reservation.yaml specific to that provider. This and the json schema validation from enoslib implement BeyondTheClouds#174 and implement BeyondTheClouds#315
Would be useful to have a
--validate
flag that validates the YAML for a given subcommand. For example:enos up --validate
would check whether the YAML file contains all the necessary info for executing theup
operation.The text was updated successfully, but these errors were encountered: