Terraform-provider-azuredevops: Agent Pool - Azure virtual machine scale set

[aleqsss]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

The 'Azure virtual machine scale set' pool type of agent pools, inside of Azure DevOps, has now been released and is publicly available, since the (what I can see) version 6.0 of the Azure DevOps REST API. This makes me think that it would be suitable to be able to configure such, from this provider.

As you can see in the documentation, it now implementes the TaskAgentPoolOptions definition which allows you to specify, amongst others, the elasticPool property.

New or Affected Resource(s)

Affected Resources:

• azuredevops_agent_pool

Affected Data Sources:

• azuredevops_agent_pool
• azuredevops_agent_pools

References

From what I can see, this provider is using the azure-devops-go-api which, at the time of writing, doesn't implement the elasticPool / TaskAgentPoolOptions. Because of this I've created the following issue in that repository:

• Add new taskagent resource functionality #90

[aleqsss]

I'm interested in working/contributing on this issue, but I'm impeded because as of my understanding, the azure-devops-go-api is using an internal tool/code generator to generate the SDK.

[simongottschlag]

@xuzhang3 would it be possible for you to ask internally at Microsoft what the plans are for the updated SDK?

@aleqsss has been waiting for a reply for quite some time and would be great to understand what the plans are.

I created the following more than a week ago and still nothing: https://github.com/microsoft/azure-devops-go-api/issues/93

Thank you 😊

[xuzhang3]

@simongottschlag Sure, I will update the information when I got response from service team.

[aleqsss]

Thank you for your input, @simongottschlag and @xuzhang3.

Unfortunately I haven't received any feedback whatsoever, on the Add new taskagent resource functionality #90 issue/feature request. So an information update in regards of the plans of updating that SDK, would be highly appreciated @xuzhang3. Thank you for investigating this internally.

[aleqsss]

@xuzhang3 were you able to get any response from the service team?

Thank you! 🙂

[xuzhang3]

Hi @aleqsss We have some internal progress, I will update it here if there is any update.

[aleqsss]

Thank you @xuzhang3, I appreciate that!

[stefanes]

@xuzhang3 Any update on the internal progress you mentioned?

[xuzhang3]

@stefanes I get some repsonse internal that v6.x will be released but do not have the timeline

[aleqsss]

@xuzhang3, any updates in regards of the timeline? 🙂

[daniel-anova]

Thank you for your input, @simongottschlag and @xuzhang3.

Unfortunately I haven't received any feedback whatsoever, on the Add new taskagent resource functionality #90 issue/feature request. So an information update in regards of the plans of updating that SDK, would be highly appreciated @xuzhang3. Thank you for investigating this internally.

Wouldn't they be using AutoREST like the Azure SDK?

[mvanderlyn27]

Any update on the v6.x release?

[xuzhang3]

No good news, the SDK repo is in low activity. A workaround I thinking is embed the new features as a patch in this repo and handle the sdk ourselves. DevOps swagger: https://github.com/MicrosoftDocs/vsts-rest-api-specs

[ramsateesh]

Is this coming up anytime soon ? Needed this like yesterday.

[aleqsss]

Thank you for your input, @simongottschlag and @xuzhang3.
Unfortunately I haven't received any feedback whatsoever, on the Add new taskagent resource functionality #90 issue/feature request. So an information update in regards of the plans of updating that SDK, would be highly appreciated @xuzhang3. Thank you for investigating this internally.

Wouldn't they be using AutoREST like the Azure SDK?

If you look at the filed issue https://github.com/microsoft/azure-devops-go-api/issues/90 (mentioned in this issue description) you can see that it seems like they are using some internal tool for generating this. 🙂