An entirely new way to manage Environments
Our newest improvement to how customers can manage their integrations in ONEiO is the ability to view configurations and synchronize changes between the QA and PROD environments.
In the new Environments view you’ll see a complete representation of what endpoints, message types, entity types, and rules are configured in the QA and PROD environments. The differences view highlights where there are any differences in configuration in either environment.
ONEiO offers Enterprise and Service Provider customers the ability to manage integrations in two separate environments, QA and PROD. Now there is an easy way to see what has been configured in each of these environments and synchronize any changes.
To access the Environments view, look for the Environments button on the right side of the top navigation. The new view displays QA and PROD side by side at every object level, from endpoints to entity types and message types down to the individual rules. Clicking on the “Sync Mode” button will take you through the steps to synchronize any objects you have selected.
If you have previously used the routing rule import/export to move routing rules between your QA/PROD environments, we encourage you to try out the new Environments view and Sync Mode.
See our documentation for more information on how to best utilize the Environments view and what to consider when synchronizing environments:
Read more about how the Environments view functions
Read more about how Sync Mode functions
If you have more questions regarding the new functionality, you can post them below in the comments section or reach out to our support team at support@oneio.cloud.
Comments
Hi Daniel & David!
Thanks for the suggestion, we are currently working on making it possible to handle environment-specific values in the syncing process. Stay tuned for the update :)
-Petteri
Please add functionality to manage environment-level variables so that this sync could be more useful. We won't be able to use the sync feature in most of the cases as we have some environment specific values which are different between QA and Prod.
Thank you!
+1 to this. Target project, creator user id, etc are often different.
Thanks!
Please sign in to leave a comment.