📄️ Environments in Multi-Cloud Runtime
The primary objective of enabling environments in Boomi flow is to facilitate the management of flow releases through the Multi-Cloud Runtime (MCR). This setup allows precise control over how flows are deployed and executed across different environments, such as development, testing, and production.
📄️ Enabling and Configuring MCR Environments
To start using MCR environments, a tenant Administrator must first enable them in your tenant. Once the feature is enabled, you have both MCR nodes and environments turned on for your tenant.
📄️ Adding a Flow to a release
To add flows to an existing release:
📄️ Adding a Theme to a release
To add a theme to an existing release:
📄️ Promoting a release to the next environment
Promote a release to deploy it to the next environment in the development life cycle.
📄️ Running a Flow in an environment
To execute a Flow in a specific environment, use the following URL format:
📄️ Rolling back a release
Rollback follows the same procedure as deployment, including MCR node notification and success/failure messaging.
📄️ Environment variables
During the ping process, the system synchronizes environment variables to the MCR node as part of the tenant settings. When you create or update an environment variable, wait for the next ping to complete. Once this ping occurs, the system will successfully propagate your changes to the MCR node.
