Denodo Code Promotions
Table of Contents
Process
Promotion of code can be done in the Solution Manager (see Denodo Servers and URLsarchived ).
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.
Create a revision. All revisions should use DEV as their source environment.
Select your revision elements
If making role changes, be sure to include any objects directly associated with that role so the necessary VQL is generated to update permissions
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.
Give revision a name and description and save
Validate your revision against STAGE and PROD
Announce the revision in #revisions in the Denodo team in Teams asking for it to be deployed at the next Monday deployment session.
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.