...
| Drawio | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Note that the view show the difference in a human readable format, in the form of a text difference. For complex objects, such as the workflows, the difference may however be hard to read. It is always best for the changes to be reviewed and selected by someone who is familiar with the changes done on the project.
Git Synchronization
This view will allow you to commit, push and pull to the remote Git repository.
Note that the view does not automatically refresh after actions, refresh the view to get an updated status.
In general, the recommended set of actions is:
review the changes, approve them (commit) or reject them (rollback)
pull the changes from the remotes servers, if any, these will be highlighted by a down arrow
push the changes to the remote server, this action will be highlighted by an up arrow.
In general, you should end with a view without any warnings, changes, or suggested actions.
Integrate
Your bot is typically one bot in a deployment chain such as:
Production → Pre-production → Dev
Provided that the versions meet certain requirements, you can merge the changes from the sibling environments. For example, if you are in Pre prod, you could:
Retrieve the changes made in production. While it is not usual to have configuration changes done directly in production, this may occur for simple things like messages or corrective actions that would have been done directly inside the production environment.
Retrieve the changes made in a development environment. This is the expected path. Developers will work on dev and commit/push their changes after they are done. You could merge the changes to your preproduction environment to get a chance to validate them before later retrieving them in production.
Apply
As stated in the view, this action will:
Load the configuration from files, effectively replacing the content in the DB with the content found in the files.
Retrieve possible corrections and enhancements made on the product
Restart a few processes to ensure all changes are fully loaded and in place in the product
Executing the action in this view result in a downtime of a few minutes.