Feature Request: Force unlock workflow/pipeline

[matt-FFFFFF]

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

Inspiration: https://github.com/terraform-azurerm-examples/terraform-enterprisescale-starter/blob/main/.azure-pipelines/templates/tf-force-unlock.yml

Describe the solution you'd like

Additional context

[matjahs]

Hi, I would like to try this (would be my first issue). Anything I need to be aware of/need to know outside of the contribution guidelines?

[jaredfholgate]

Hi @matjahs. The only thing I was thinking about this morning is that it is slightly more complex than I thought when I added the label. In that we now use governed pipelines, so would need to add this as a template and ensure the plan service connection and federated credentials support this.

So would need updates to:

• ci_cd folder: Needs new pipeline and template for each VCS
• terraform.tfvars needs updating to create the pipelines and associated permissions for each VCS bootstrap

I think those are the only two areas that need updating.

[matjahs]

@jaredfholgate I will wait to see if something else comes along during my vacation next month. Work has gotten really busy this week.

[jaredfholgate]

There are other measures in place to avoid state file locking, but having a pipeline to unlock the state could still be useful for error states.