During implementation, you may want to set up data operations. We recommend building and testing an asset in a staging environment before using it in a production environment. But who wants to manually rebuild or duplicate an asset after doing all that hard work?
For that reason, we support asset promotion, which allows you to move assets you’ve tested in staging to production environments. Promoting assets saves you time and prevents introducing errors when manually rebuilding across environments.
You may want to use asset promotion when you’re:
- Creating data operations (learn about Redox data operations) during a new implementation project.
- Completing testing before go-live during an implementation project.
- Troubleshooting an issue on a live subscription.
Currently, we only support asset promotion for config modifiers—but stay tuned! Learn how to promote a config modifier.
Promoting an asset creates an association between the asset that exists in staging and the asset that exists in production. This allows you to see when the production asset may be out of date. For example, any edits to a staging config modifier creates a new version of the asset. To keep your changes in sync with production, you may want to re-promote the asset to production.
However, links to subscriptions aren’t part of the promotion. This means links to staging subscriptions won’t carry over to your production environment. Instead, you have to create and manage links to subscriptions in each environment separately.
If you delete the asset in either environment, it removes the association as well.