Split variable creation from variable group creation to allow create/update/delete variables in a variable group and key vault independently

[Marcus-James-Adams]

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

Currently, we set variables as part of the resource "azuredevops_variable_group" This means that all variables must be created or updated at the same time However, there are business reasons such as having an environment or stage level variable group where you would want to store values from more than or terraform module or code run.

If variables were managed in the same way as key vault secrets you could update them independently of each other.

New or Affected Resource(s)

resource "azuredevops_variable_value" "this_value" {
  project_id   = data.azuredevops_project.main.id
  variable_group_id =azuredevops_variable_group.main.id
  name         = "myname"
  value          = "myvalue"              
}

• azuredevops_XXXXX

• #0000

[drdamour]

this would help me as my single code repo has the tf module code for my app as well as my app code to deploy. For deployment i need values from a variable group with secrets...but that module is what creates the variable group in the first place. i'd much rather create the variable group in the UX and then set secrets on it with the provider

[Marcus-James-Adams]

@xuzhang3 , As we have a support contract with Microsoft, is there anything we can do, somebody to speak to, in order to get this on the roadmap?

[DaleyKD]

This is almost 2 years later, and this is the reason I can't use this provider. @xuzhang3 : Please; this NEEDS to be done yesterday.