I was just wondering, if anyone else is facing this issue or if this is something because of how we did set up the action.
At the moment we use the "ROC - Assign Servers" action in our pre-deployment, but this action can only be executed if the user has environment admin rights. This hinders us in setting up more detailed permissions, where we for example just allow a couple of user to deploy specific processes in one environment, but of course you always need to run the pre-deployment.
This is our setup:
I just tried the same and manage to assign the servers in pre deployment step while running with user that have permissions only to run releases and release designer in the specific environment. (Tested in V5.5.2-324)
What was the error message that you get?
Please make sure the server is already assign to the environment and to the specific server type
thanks for testing it on your side. I will try it again asap and let you know the error message.
just to make sure: which version did you use for your testing?
I tested in version 5.5.2-324
I tried it again with a testuser, which I gave the permissions:
- Can View Application
- Can View Design Components
- Can View Execution Components
- Release Template Designer
- Release Designer
- Can Execute All Processes
- Can Execute All Releases
When creating the deployment I check the "assign all servers" checkbox (we need this, as we also have server types where all environment servers are included and that are used for general flows)
the error I'm getting directly points to missing permissions:
although the servers are assigned to the environment:
As I said, when I'm giving the testuser environment admin rights, everything works.
We're currently running on ROC Version 220.127.116.11
Do you know of any fixes or changes with this action in your version?
I checked 5.5.2-324 fix README file and found the following description:
"- Fix requirement to be env-admin to be able to assign servers to server type"
I think this exactly the problem you are facing
awesome, so there is now definitely the first reason, that we need to upgrade with the next major release.
thanks for checking this jacky!