You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When quantity of the resources in a single stack becomes too big, stack's apply and plan operations inevitably become slow.
Describe the solution you'd like
I'd like terramate cloud to collect stats of resource mutations and calculate ratio of resource versus state mutations. And if it turns out that there are some resources that do not change for a decent number of state changes, suggest the user to split the stack.
If the stack is a connected graph, terramate can render a new HCL that adds data sources and output variables to maintain the consistency of the original graphs in two different stacks.
Describe alternatives you've considered
The alternative is manual refactoring, which everyone understands is required, but almost no one risks it.
Is your feature request related to a problem? Please describe.
When quantity of the resources in a single stack becomes too big, stack's apply and plan operations inevitably become slow.
Describe the solution you'd like
I'd like terramate cloud to collect stats of resource mutations and calculate ratio of resource versus state mutations. And if it turns out that there are some resources that do not change for a decent number of state changes, suggest the user to split the stack.
If the stack is a connected graph, terramate can render a new HCL that adds data sources and output variables to maintain the consistency of the original graphs in two different stacks.
Describe alternatives you've considered
The alternative is manual refactoring, which everyone understands is required, but almost no one risks it.
Additional context
hashicorp/terraform#35755
The text was updated successfully, but these errors were encountered: