Open robertscully-wpp opened 6 months ago
@robertscully-wpp you might not have to given #747 is released in v1.0.0
Also, a workaround was mentioned in the comments at https://github.com/microsoft/terraform-provider-azuredevops/pull/747#discussion_r1420241486
@jubr thanks for the feedback on here, will have a read through the comments and release notes.
Community Note
Description
I have been making use of Federated Credentials for app registration to create dynamic tokens for Terraform executions using the Azure provider.
I would like to make use of the features of the PAT lifecycle API, as documented here, to generate an ephemeral PAT for managing Azure Devops using an Entra App Registration.
In this scenario, when an App Registration is configured to have Azure Devops API access with the user_impersonisation delegated permission, is it possible to use the same OIDC mechanism that the Azure provider uses to:
New or Affected Resource(s)
Potential Terraform Configuration
References