hashicorp / hashicorp/terraform

allow manual remote state locking -> force-lock state feature

Open
#36,928 1 comment 13 reactions 0 assignees View on GitHub
enhancement new
Dominant language
Go
Stars
49.7k
Forks
10.6k
Avg merge
21h 30m
Merged PRs (30d)
100

Description

### Terraform Version

```shell
1.11.3.
```

### Use Cases

Prolonged maintenance on part of an infrastructure declaration

### Attempted Solutions

https://github.com/minamijoyo/tflock - outdated solution to the cause

### Proposal

let's have **terraform force-lock**, as we've already **terraform force-unlock** it just makes sense. I want to declare my infrastructure not to be touched to my team, and layer this accordingly. My solution would be to
- Inform my team
- Lock my state
If possible, allow state to be used by me for the day, but not for my colleagues?

### References

- #17203

Contributor guide

Open the contributing guide

Research direction

Start by reading the existing terraform force-unlock command and the discussion in issue #17203. Determine the entry points and state-locking behavior involved; done should be a reviewed force-lock capability that prevents unintended team changes while addressing the stated personal-use requirement.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.