Requirement ID Generation and RST Validation

The new check.py script will now perform a variety of
actions to simplify updates and ensure specific
practices are followed for each update.

The script has been integrated with tox and
will run whenever the documentation is created.
It can also be ran separately by just invoking
python check.py.

The script will perform a variety of automatic
updates where possible, and provide a warning
where auto-updates are not possible.

The expecation is that all warnings are addressed
before submitting for review, but given it is a
new feature warnings do not block validation at
this time.

Here is a summary of the warnings and updates:

Warnings:
- Requirement missing required attributes
- Invalid values for attributes
- Invalid section header usage in any file
- :keyword: and requirement mismatch

Auto Updates:
- Assigning :id: on new requirements where an ID missing
- Adding :introduced: attribute on new requirements
- Adding/correcting :updated: attribute on changed requirements

Issue-ID: VNFRQTS-896
Signed-off-by: Lovett, Trevor <trevor.lovett@att.com>
Change-Id: I283441330a139aa1c6e2e79f0c54c5979bf44642

1 files changed, 7 insertions, 7 deletions

diff --git a/docs/Chapter8/VNF-License-Information-Guidelines.rst b/docs/Chapter8/VNF-License-Information-Guidelines.rst
index 94815f0..4df9cbd 100644
--- a/docs/Chapter8/VNF-License-Information-Guidelines.rst
+++ b/docs/Chapter8/VNF-License-Information-Guidelines.rst
@@ -71,7 +71,7 @@ One or more entitlements can be defined; each one consists of the
 following fields:
 
 Table C2. Required Fields for Entitlements
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 +---------------+-----------------------------------+-------------+-----------+
 | **Field Name**| **Description**                   |**Data Type**| **Type**  |
@@ -136,7 +136,7 @@ License Keys are not required. Optionally, one or more license keys can
 be defined; each one consists of the following fields:
 
 Table C3. Required Fields for License Keys
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 +---------------+-----------------------------------+--------------+----------+
 | **Field Name**| **Description**                   | **Data Type**| **Type** |
@@ -214,7 +214,7 @@ example:
 -  use is allowed in Canada
 
 Table C4. Required Fields for Location
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 +------------------+--------------------------------+--------------+----------+
 | **Field Name**   | **Description**                | **Data Type**| **Type** |
@@ -262,7 +262,7 @@ Limit on the length of time the software may be used. For example:
 -  entitlement valid from 15 May 2018 thru 30 June 2020
 
 Table C5. Required Fields for Time
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 +------------------+-------------------------------+--------------+-----------+
 | **Field Name**   | **Description**               | **Data Type**| **Type**  |
@@ -325,7 +325,7 @@ Limits based on how the software is used. For example:
 -  use is limited by software release
 
 Table C6. Required Fields for Usage
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 +------------------+-------------------------------+---------------+----------+
 | **Field Name**   | **Description**               | **Data Type** | **Type** |
@@ -374,7 +374,7 @@ make use of the software. For example:
 -  allowed to be used only for government entities
 
 Table C7. Required Fields for Entity
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 +------------------+--------------------------------+--------------+----------+
 | **Field Name**   | **Description**                |**Data Type** | **Type** |
@@ -429,7 +429,7 @@ any aggregation function (e.g., peak or average users), and aggregation
 interval (day, month, quarter, year, etc.).
 
 Table C8. Required Fields for Amount
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 +------------------+---------------------------------+-------------+----------+
 | **Field Name**   | **Description**                 |**Data Type**| **Type** |