-
Suggestion
-
Resolution: Won't Do
-
None
-
0
-
1
-
Currently in our brand we have a wide user base who use their own agents. The Bamboo environment is managed by a set of admins, and whenever the developers or automation engineers needs to administer an agent (e.g.: agent capabilities etc) unless permission is given, that engineer cannot do the needful in the interface.
There is a file that can be put in the remote agent bin folder called bamboo-capablities.properties .... however we have found that this only allows the engineer to bootstrap the agent to Bamboo. Once a KVP is put there and loaded in the interface, if that KVP is removed from the file and the agent is restarted, that KVP persists in the interface.
Please allow for administration to have granular permissions on agent configurations. Thanks
- incorporates
-
BAM-16189 As a Bamboo admin I want a way to limit a user's access to remote agent configuration.
- Closed
- is incorporated by
-
BAM-20412 Bamboo for Teams - self-contained projects
- Future Consideration
- is superseded by
-
BAM-20412 Bamboo for Teams - self-contained projects
- Future Consideration
- is mentioned by
-
PSR-266 You do not have permission to view this issue
Hi everyone,
Thank you for your interest in this issue.
While this suggestion has gathered significant interest, we're not going to implement it in a way described here. We see however that delegation of agent administration will be a part of the self-contained project story (BAM-20412) and any future progress of this should be tracked there.
To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.
Kind regards,
Bamboo Team