Once configuring a stack following here, you can clone the stack to the same project or a different project.
For example, once a stack configuration is created on one project, an authorized user can easily clone the stack configuration and update some configuration such as cluster parameters and target environment settings and deploy the cloned stack to the upper environments such as staging or production environment.
To clone a stack:
Click the "Clone" button on the top of the stack configuration page.
Enter a new stack name, select the target project to be cloned.
Be aware the user must have permission for Clone action and be the user of the target project. The cloned stack status will be Not deployed.
Benefits of Clone:
With a build once, deploy anywhere approach, the time could be significantly reduced by just cloning the stack. The same Architecture Blueprint can be easily deployed from development to production.
Cloning enables you to reuse the same skill sets for development and operations no matter where the stack is built and deployed.
You can spend more time trying to solve flaws within your business applications, but not for replicating Platform infrastructure for troubleshooting. For example, you can debug the production problems by cloning the production stack into an isolated environment. You can install production business applications into the cloned production stack where you can debug the production problems, not impacting the production stack.
There would usually be fewer errors in promoting applications from lower to upper environments using the cloning feature in dpStudio (Web application) providing template deployment.
What's Next