[VNFRQTS] updates to Heat Orch Format & 1 new req

Issue-ID: VNFRQTS-746
Signed-off-by: weinstock, alan <aw2574@att.com>
Change-Id: I1ba08be5c791353cd3163d2ff6d14bd26209cb3d

diff --git a/docs/Chapter5/Heat/ONAP Heat Orchestration Template Format.rst b/docs/Chapter5/Heat/ONAP Heat Orchestration Template Format.rst
index a23f217..e4202d3 100644 (file)
--- a/docs/Chapter5/Heat/ONAP Heat Orchestration Template Format.rst
+++ b/docs/Chapter5/Heat/ONAP Heat Orchestration Template Format.rst
@@ -119,6 +119,9 @@ parameters
 
       immutable: <true | false>
 
+      tags: <list of parameter categories>
+
+
 This section allows for
 specifying input parameters that have to be provided when instantiating
 the template. Each parameter is specified in a separate nested block
@@ -349,10 +352,8 @@ The constraints are defined as a list with the following syntax
 .. code-block:: yaml
 
   constraints:
-
-    <constraint type>: <constraint definition>
-
-    description: <constraint description>
+    - <constraint type>: <constraint definition>
+      description: <constraint description>
 
 ..
 
@@ -402,15 +403,14 @@ The syntax of the ``allowed_values`` constraint is
 
     allowed_values: [ <value>, <value>, ... ]
 
-    Alternatively, the following YAML list notation can be used
+Alternatively, the following YAML list notation can be used
 
-    allowed_values:
-
-    - <value>
-
-    - <value>
+.. code-block:: yaml
 
-    - ...
+    allowed_values:
+      - <value>
+      - <value>
+      - ...
 
 immutable
 ++++++++++++
@@ -429,6 +429,19 @@ that defines whether the parameter is updatable. A Heat Orchestration Template
 stack update fails if ``immutable`` is set to ``true`` and the parameter
 value is changed.  This attribute ``immutable`` defaults to ``false``.
 
+tags
+++++++++++++
+
+.. req::
+    :id: R-225891
+    :keyword: MAY
+    :target: VNF
+    :introduced: el alto
+
+    A VNF's Heat Orchestration Template parameter declaration
+    **MAY** contain the attribute ``tags:``.
+
+
 .. _resources:
 
 resources