Table of Contents

Process

Promotion of code can be done in the Solution Manager (see Denodo Servers and URLs )

...

.

The process below outlines how revisions 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.

   Image Added

   1. Select your revision elements

      1. If making role changes, be sure to include

      all

      1. any objects

      in any VDB

      1. directly associated with that role so the necessary VQL

      for permissions updates

      1. is generated

2. Deploy revision to STAGE

3. Have a peer review the revision

4. Once approved, promote to PROD

Revision Tracker

1. 1. 1. to update permissions

      2. DO NOT promote any dev roles when promoting to STAGE or PROD. Only promote read roles. This will ensure that objects are read only outside of the dev environment.

   2. Give revision a name and description and save

   3. Validate your revision against STAGE and PROD

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

2. 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

...