There are some different scenarios that can occur during the validation process, that you should take note of. These scenarios may occur if a conflict has taken place during the pull or commit stages. Such scenarios are listed below:
Case 1
When a user pulls configuration from the target environment, Configuration Manager will check if the revision code for each object is equal to the revision code from the last successfully committed object.
If there is a conflict, Configuration Manager will present the user with a warning message. This conflict may have occurred because the user has tried to commit an object that is not present in the pull stage.
Case 2
When a user commits changes to the target environment, Configuration Manager will check if the new target revision code for each object is not equal to the revision code from the last successfully committed object. If there is a conflict during the commit stage, Configuration Manager will present the user with a warning message, and a suggested course of action.
If there is a conflict during the commit stage, Configuration Manager will present the user with a warning message, and a suggested course of action.
Case 3
When a user commits changes to the target environment, Configuration Manager will check whether each object's new target revision code is different to the latest revision code pulled from target (expected_revision).
If there is a conflict during the commit stage, Configuration Manager CLI will present the user with a warning message informing them that there is a conflict, and Configuration Manager will give the User a suggested course of action.
Case 4
When the user commits configuration changes to the target environment, Configuration Manager will send the new objects to deploy along with their “expected_revision” (the revision code Dalet FlexCM believes is in Dalet Flex Core updated in the latest pull target) to Dalet Flex Core. Then Dalet Flex checks that the “expected_revision” for the object is equal to the revision of the actual object.
If there is a conflict during the commit stage, a warning message will be presented informing the User that there is a conflict, and will give the user a suggested course of action.
Comments
0 comments
Please sign in to leave a comment.