...
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 include any dev roles in your revisions, read roles only. This will ensure that objects are read only outside of the dev environment.
If you want a scheduler job to run as part of your deployment you can right click the job and click Execute job when revision is deployed. Make sure to also click the checkbox for the job.
Give revision a name and description and save
Validate your revision against STAGE. This step will give you the ability to set properties for connections, allowing you to define new URL’s and credentials for connections deployed to STAGE. This will have to be done against PROD as well, but must be done by a Denodo admin.
Deploy your revision to STAGE, confirm that it deploys successfully, and test the revision elements. If you encounter issues, delete your revision and repeat steps a through d until successful.
Announce the revision in the Revisions channel of 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 validated against PROD and deployed. If issues are found, you will be asked to resolve them before deployment. URL’s and credentials for new datasources for PROD will need to provided to admins for entering.
...