Hi,
We're like to clarify the best-practices for promoting graphs and listeners between development and Test sandboxes to a Production sandbox.
Environments would be nominally equivalent, but database names, credentials and some paths would differ.
A concept we'd need to support is that code does not change between sandboxes. Parameter files could change for path, database name and credentials.
Recommendations and tips?
Thanks,
We're like to clarify the best-practices for promoting graphs and listeners between development and Test sandboxes to a Production sandbox.
Environments would be nominally equivalent, but database names, credentials and some paths would differ.
A concept we'd need to support is that code does not change between sandboxes. Parameter files could change for path, database name and credentials.
Recommendations and tips?
Thanks,
-
Hi Tom,
It is recommended to:
* externalize connections
* use externalized parameters for all other things (paths, ...)
Externalized objects can be stored into separate directory. By multiple versions of such directory in multiple environments you can achieve your goals.
For listeners, there is currently no way how to migrate them. However, we have "configuration migration" feature in our plans for near future.
Please sign in to leave a comment.
Comments 1