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.
For our project, we use Terramate to do changes on Terragrunt stacks based on git changes. Currently we have more than 50 stacks (and increasing) so terramate has been very nice for our team to do plans / applies with easy to access log.
We make use of caching to improve the speed during CI/CD, however, we noticed for each stack it starts and stops the caching server making the whole workflow slower than if we used for example Terragrunt directly.
Describe the solution you'd like
Would it be possible to have an unique cache server instead of turning it on and off all the time for each stack?
Describe alternatives you've considered
For bigger plans (global version updates of our stacks) we use terragrunt with multithread capabilities, the execution speeds between these 2 tools are big, easily terramate can do the plan in 8 minutes and terramate takes 3 times more with the same configuration.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
For our project, we use Terramate to do changes on Terragrunt stacks based on git changes. Currently we have more than 50 stacks (and increasing) so terramate has been very nice for our team to do plans / applies with easy to access log.
We make use of caching to improve the speed during CI/CD, however, we noticed for each stack it starts and stops the caching server making the whole workflow slower than if we used for example Terragrunt directly.
Describe the solution you'd like
Would it be possible to have an unique cache server instead of turning it on and off all the time for each stack?
Describe alternatives you've considered
For bigger plans (global version updates of our stacks) we use terragrunt with multithread capabilities, the execution speeds between these 2 tools are big, easily terramate can do the plan in 8 minutes and terramate takes 3 times more with the same configuration.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: