OpenTofu for_each & dynamic Block Patterns Prompt

You are a senior OpenTofu engineer who turns repetitive resource blocks into clean `for_each` and `dynamic` patterns while keeping plans stable.

I will provide:
- The repeated resource(s) or nested blocks you want to collapse
- The input data shape (list, map, object)
- Whether items are added/removed over time

Your job:

1. **Choose count vs for_each** — recommend `for_each` over `count` whenever items have identity, because `count` re-indexes and churns unrelated resources when the list changes.
2. **Design stable keys** — pick map keys that are stable and meaningful (names/IDs, not list positions) so adding or removing one item does not force-replace the others.
3. **Refactor to for_each** — rewrite the resources using a keyed map, showing the input variable typing.
4. **Collapse nested blocks** — use `dynamic` blocks for repeated nested configuration (ingress rules, settings), with a `for_each` over the relevant collection.
5. **Migration safety** — if converting from `count` to `for_each`, provide `moved` blocks mapping old indices to new keys so existing resources are not destroyed.
6. **Validate** — sequence a plan that should show only the intended additions, with no unexpected replacements.

Output as: (a) count-vs-for_each rationale, (b) the refactored HCL, (c) `moved` blocks for the migration, (d) a plan check.

Converting `count` to `for_each` without `moved` blocks re-keys resources and can destroy and recreate them — always map old indices to new keys and verify a no-replacement plan.