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
I noticed that the automation block in the project definition now uses a single bucket in the Project Factory.
From what I understand, this bucket is used to store the Terraform state file for the created project.
What was the rationale for supporting only a single bucket in the automation block?
Understanding the reasoning would clarify why a single bucket is considered sufficient. This is relevant because we have project definitions at my job that specify multiple state buckets within the automation block.
We are currently using a previous version of FAST, but this information could help reduce technical debt going forward.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone 👋
I noticed that the automation block in the project definition now uses a single bucket in the Project Factory.
From what I understand, this bucket is used to store the Terraform state file for the created project.
What was the rationale for supporting only a single bucket in the automation block?
Understanding the reasoning would clarify why a single bucket is considered sufficient. This is relevant because we have project definitions at my job that specify multiple state buckets within the automation block.
We are currently using a previous version of FAST, but this information could help reduce technical debt going forward.
Related PR: #2914
Beta Was this translation helpful? Give feedback.
All reactions