cisagov / cisagov/skeleton-packer
Consider removing Terraform `moved` blocks once they are no longer needed
- Dominant language
- HCL
- Stars
- 9
- Forks
- 4
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
# 💡 Summary #
@mcdonnnj suggested removing the Terraform `moved` blocks introduced in #355.
## Motivation and context ##
I personally think the `moved` blocks can be left in, but you can enjoy my back-and-forth with @mcdonnnj [here](https://github.com/cisagov/skeleton-packer/pull/355#pullrequestreview-2223646409).
Contributor guide
Research direction
Start by reviewing PR #355 and the linked review discussion to understand why the Terraform `moved` blocks were introduced. Locate those blocks in the repository and determine whether their state-migration purpose is still needed; done means reaching a clear decision and removing them only if the project agrees they are no longer required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- terraform
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100