As we know, if someone is already viewing/modifying a flow, another user could not make any changes to the flow and we could see a pop-up saying that the flow is already being updated by some other user. I would like to understand, if it is the same behavior in case of updating Environment Parameter?
Does CA-RA locks the Environment Parameter while a deployment is in progress on that environment? so that no other user could modify the parameter while deployment is in progress?
We have a scenario, where users are changing the environment parameters and they expect that it should be reflected as and when their deployment request is picked up. However, what we see is, the environment parameter does not get updated all the time, sometimes it does not update the parameter if there is already a deployment in progress on that environment.
We need to have a mechanism, so that, environment parameter could be tagged to the deployment id. as and when the deployment starts it should refer to that version of environment parameter.