Versions Compared

Version Old Version 115 New Version 116
Changes made by

Matthew Girard

Matthew Girard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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 any objects directly associated with that role so the necessary VQL is generated to update permissions

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

    2. Give revision a name and description and save

    3. Validate your revision against STAGE and PROD. This step will give you the ability to set properties for connections, allowing you to define new URL’s or and credentials for connections deployed to STAGE and PROD. This will have to be done against PROD as well, but must be done by a Denodo admin.

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

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

  3. The admins will review your revision for security. If there are no issues, the revision will be deployed to STAGE and PRODvalidated 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.

Note that every connection in Denodo gets environment variables created in STAGE and PROD as part of the validation process. These variables allow you to deploy connections with different URLs in STAGE and PROD without creating separate connections and views.