We use a fully automated process to "refresh" our farm of linux build agents. This includes a full tear-down of the filesystem and binaries, and re-installing all build tools, JDKs, etc. This ensures that individual jobs and plans don't degrade the system overtime.
We keep the Agent name and ID the same for historical reporting, but would like means to purge the existing capabilities from our process. This allows us to retire old capabilities/versions without the need to manually click, and confirm, dozens of individual capabilities on ten's of agents.
A DELETE call to a REST URL for each agent's ID would be amazing useful for our support of commodity agents.
[BAM-14260] Expose ability to delete/remove agent capabilities via REST API
If folks are looking to delete agent specific capabilities for automated maintenance, please check out https://eddiewebb.atlassian.net/wiki/display/AAFB/Agent+Capability+API+Operations and if that's what you need, you can install the 2.0-SNAPSOT of my Agent APIs Plugin for Bamboo plugin now, or wait for the 2.0 version of Agent APIs in the atlassian marketplace in the next few weeks.
The plugin is free (open source) and of my own free time effort, so feedback is encouraged, but be nice 
Christina Forney
added a comment - This is hugely important in the direction that we're taking our CI. Adding this capability would be a gigantic value add to my team/company.
Christina Forney
added a comment - This is hugely important in the direction that we're taking our CI. Adding this capability would be a gigantic value add to my team/company. 
Deleted Account (Inactive)
added a comment - +1 from me, this is in a way related to BAM-12894:
If capabilities get changed on remote agents (i.e. by chef runs) we don't find a way to advertise the changes to the server:
So it would be great to either have the:
a.) ability to delete the server side definition of capabilities (as they don't get overwritten)?
b.) ability to delete the whole agent (as we can deploy new agents easily and the capabilities change constantly)?
Deleted Account (Inactive)
added a comment - +1 from me, this is in a way related to BAM-12894 :
If capabilities get changed on remote agents (i.e. by chef runs) we don't find a way to advertise the changes to the server:
So it would be great to either have the:
a.) ability to delete the server side definition of capabilities (as they don't get overwritten)?
b.) ability to delete the whole agent (as we can deploy new agents easily and the capabilities change constantly)?
We're doing a lot with Chef to automate agent creation and consistency and having the ability to create the capabilities initially is a good help, but a rest api to maintain them as things changed would be outstanding. We could link this right into our chef cookbooks and would make agent management much easier to deal with.