Support for creating, configuring and removing Agent pools
I would like to be able to create and configure Agent Pools in Azure DevOps. This would include things such as:
- Creating a new Agent pool.
- Configure settings, such as auto-provioning and maintenance jobs.
- Configure the security settings on the Agent pools.
- Removing Agent pools.
I looked in the available cmdlets and it seems the module doesn't provide the functionality. I am new to the module, so perhaps I overlooked. Any insights on this would be appreciated. Thanks allot!
Hey, nice idea. Let me check that if I can provide you with some cmdlets.
I made a quick research and found the following documented APIs to create cmdlets from:
- Managing Agent Pools for adding, deleting, updating and retrieving
- Connecting pools with projects which makes an agent pool available to a project by adding, deleting and retrieving
The following do not have a documented API as far as I can see:
- configure maintenance jobs
- configure permissions
So I could start implementing the other two things.
Thanks for the quick response! It would be awesome if these things could be integrated in de module.
Like I mentioned, I’m new to the module. But please let me know if there’s anything I can do to help.
Given the links above you should be able to call the API with the module today. Just use the
Invoke-VSTeamRequest
Invoke-VSTeamRequest can all any API even if we have not had time to wrap it.
Working on this now. I will start with adding, updating and removing agent pools.
I started implementing the following things and want them to be merged first
- delete
- add
- update
Agent pools and their basic settings like auto-provision, description, name, auto-update
@rwaal you might want to check the connected PR to see if that fulfils your request.
Hi, nice to see this is going somewhere. Will this include support for VM scalesets as well?
Probably not yet (I forgot what I implemented). The PR is waiting for Donovans Review. But it can be implemented afterwards.
Just checked. It does not. Has to be implemented first. You wanna give it a try after merging this one?