...

The process below outlines how to create. Each revision should be added to the Revision Tracker table below for the purpose of tracking approvalsrevisions are created and deployed. Revisions are reviewed by admins and deployed every Monday. Before creating revisions, make sure you’ve done adequate testing of your code.

1. Create a revision. All revisions should use DEV as their source environment.

   

   1. Select your revision elements

      1. If making role changes, be sure to include all any objects in any VDB directly associated with that role so the necessary VQL for permissions updates is generated to update permissions

      2. DO NOT promote the any dev role roles when promoting to STAGE or PROD. Create and Only promote a read role insteadroles. This will ensure that all VDB’s/Object objects are read only outside of the dev environment.

   2. Give revision a name and description and save

   3. Create a row in the Revision Tracker below for Validate your revision

2. Have a peer review the revision and add their name under the Approved By column in the Revision Tracker once approved.

3. Deploy the revision to STAGE and perform smoke testing

4. If smoke testing passes, deploy to PROD

5. If smoke testing fails, investigate, then create a new revision to address the issues

   1. against STAGE and PROD

   2. Announce the revision in #revisions in the Denodo team in Teams asking for it to be deployed at the next Monday deployment session.

6. The admins will review your revision for security. If there are no issues, the revision will be deployed to STAGE and PROD. If issues are found, you will be asked to resolve them before deployment.

Revision Tracker