Tony Hansen | 6b903fe | 2017-09-29 17:29:52 +0000 | [diff] [blame] | 1 | check-blueprint-vs-input(1UTIL) ONAP check-blueprint-vs-input(1UTIL) |
| 2 | |
| 3 | |
| 4 | |
| 5 | NNAAMMEE |
| 6 | check-blueprint-vs-input |
| 7 | |
| 8 | SSYYNNOOPPSSIISS |
| 9 | check-blueprint-vs-input [-h] [-b BLUEPRINT] [-i INPUTS] |
| 10 | [-B BLUEPRINT_EXCLUSION_LIST] |
| 11 | [-I INPUTS_EXCLUSION_LIST] [-t] [-v] |
| 12 | |
| 13 | DDEESSCCRRIIPPTTIIOONN |
| 14 | Validate a blueprint and inputs file against each other. This looks for |
| 15 | the inputs: node of the blueprint file, the inputs used by {get_input} |
| 16 | within the blueprint, and the values found in the inputs file. The |
| 17 | files may be in either YAML or JSON formats. The names default to blue‐ |
| 18 | print.yaml and inputs.yaml. If a blueprint inputs name has a default |
| 19 | value, it is not considered an error if it is not in the inputs file. |
| 20 | If using a template inputs file, add the -t/--template option. This |
| 21 | will look for the inputs under an "inputs:" node instead of at the top |
| 22 | level. If there are blueprint nodes or inputs nodes that should not be |
| 23 | considered an error, specify them using the -B/--blueprint- exclusion- |
| 24 | list and -I/inputs-exclusion-list parameters. "check-blueprint-vs- |
| 25 | input --help" will list all of the available options. |
| 26 | |
| 27 | OOPPTTIIOONNSS |
| 28 | -h, --help show this help message and exit |
| 29 | |
| 30 | -b BLUEPRINT, --blueprint BLUEPRINT Path to blueprint file, defaults to |
| 31 | 'blueprint.yaml' |
| 32 | |
| 33 | -i INPUTS, --inputs INPUTS Port to listen on, defaults to 'inputs.yaml' |
| 34 | |
| 35 | -B BLUEPRINT_EXCLUSION_LIST, --blueprint-exclusion-list BLUE‐ |
| 36 | PRINT_EXCLUSION_LIST Comma-separated list of names |
| 37 | not to warn about not |
| 38 | being in the blueprint file |
| 39 | |
| 40 | -I INPUTS_EXCLUSION_LIST, --inputs-exclusion-list INPUTS_EXCLUSION_LIST |
| 41 | Comma-separated list of names not to warn about not |
| 42 | being in the inputs file |
| 43 | |
| 44 | -t, --inputs-template Treat inputs file as coming from template area |
| 45 | |
| 46 | -v, --verbose Verbose, may be specified multiple times |
| 47 | |
| 48 | |
| 49 | |
| 50 | ONAP {{DATE}} check-blueprint-vs-input(1UTIL) |