summaryrefslogtreecommitdiffstats
path: root/check-blueprint-vs-input/man/check-blueprint-vs-input.1
diff options
context:
space:
mode:
authorJack Lucas <jflucas@research.att.com>2020-02-03 18:21:29 -0500
committerJack Lucas <jflucas@research.att.com>2020-02-07 13:07:09 -0500
commitbad772074d0bfd4c4dcb7bdd2cbe9ca7246fc28e (patch)
tree5119178d7308c199ffdc12a5b8b1c4877a1c092b /check-blueprint-vs-input/man/check-blueprint-vs-input.1
parent86685f86e7ee03a25f913da72de5105d92c1fbba (diff)
Move k8s-bootstrap container to blueprints repo1.9.0
Cleanup of unnecessary input templates and other files Use non-templatized blueprints instead of blueprint templates Copy blueprints from blueprints/ directory into image Move reference_templates to top-level directory Issue-ID: DCAEGEN2-2041 Signed-off-by: Jack Lucas <jflucas@research.att.com> Change-Id: Ib846a96a4995eb97383f63ff764705e6277a24b0
Diffstat (limited to 'check-blueprint-vs-input/man/check-blueprint-vs-input.1')
-rw-r--r--check-blueprint-vs-input/man/check-blueprint-vs-input.150
1 files changed, 0 insertions, 50 deletions
diff --git a/check-blueprint-vs-input/man/check-blueprint-vs-input.1 b/check-blueprint-vs-input/man/check-blueprint-vs-input.1
deleted file mode 100644
index 247fbc6..0000000
--- a/check-blueprint-vs-input/man/check-blueprint-vs-input.1
+++ /dev/null
@@ -1,50 +0,0 @@
-check-blueprint-vs-input(1UTIL) ONAP check-blueprint-vs-input(1UTIL)
-
-
-
-NNAAMMEE
- check-blueprint-vs-input
-
-SSYYNNOOPPSSIISS
- check-blueprint-vs-input [-h] [-b BLUEPRINT] [-i INPUTS]
- [-B BLUEPRINT_EXCLUSION_LIST]
- [-I INPUTS_EXCLUSION_LIST] [-t] [-v]
-
-DDEESSCCRRIIPPTTIIOONN
- Validate a blueprint and inputs file against each other. This looks for
- the inputs: node of the blueprint file, the inputs used by {get_input}
- within the blueprint, and the values found in the inputs file. The
- files may be in either YAML or JSON formats. The names default to blue‐
- print.yaml and inputs.yaml. If a blueprint inputs name has a default
- value, it is not considered an error if it is not in the inputs file.
- If using a template inputs file, add the -t/--template option. This
- will look for the inputs under an "inputs:" node instead of at the top
- level. If there are blueprint nodes or inputs nodes that should not be
- considered an error, specify them using the -B/--blueprint- exclusion-
- list and -I/inputs-exclusion-list parameters. "check-blueprint-vs-
- input --help" will list all of the available options.
-
- OOPPTTIIOONNSS
- -h, --help show this help message and exit
-
- -b BLUEPRINT, --blueprint BLUEPRINT Path to blueprint file, defaults to
- 'blueprint.yaml'
-
- -i INPUTS, --inputs INPUTS Port to listen on, defaults to 'inputs.yaml'
-
- -B BLUEPRINT_EXCLUSION_LIST, --blueprint-exclusion-list BLUE‐
- PRINT_EXCLUSION_LIST Comma-separated list of names
- not to warn about not
- being in the blueprint file
-
- -I INPUTS_EXCLUSION_LIST, --inputs-exclusion-list INPUTS_EXCLUSION_LIST
- Comma-separated list of names not to warn about not
- being in the inputs file
-
- -t, --inputs-template Treat inputs file as coming from template area
-
- -v, --verbose Verbose, may be specified multiple times
-
-
-
-ONAP {{DATE}} check-blueprint-vs-input(1UTIL)