This article is how to manage each Instance of Govern while Implementation for DEV, UAT and PROD environments. These are general recommendations rather than requirements. You may chose to use DEV, UAT and PROD environments in any manner that suits your use case.
Standard Environment Usage
Generally the DEV environment is seen as a sandbox to test out new features or experiment with implementing new items. UAT is for user acceptance testing prior to launch into production. This is where user acceptance would occur. PROD contains your finalized structure and items.
Cloning Environments
For ease of promotion across environment, you may request an environment clone from one of your environments into another environment. This is most commonly one of the two directions:
- UAT into PROD - to promote new updates into PROD after user testing completes
- PROD into UAT - to clear out any new updates that didn't pass user testing and start from a fresh copy of PROD
Note that cloning environments is not the only way to promote or clear items in bulk. The standard Data360 Govern APIs can be used to POST, PUT and DELETE into PROD.
Comments
1 comment
Suhas Kotha thanks for this. Is there advice on best practice around Govern backup, e.g. whether we should be regularly performing a GET of every endpoint and saving the responses, or how best to roll back changes to some past point in time?
Please sign in to leave a comment.