Feature request: multiple s3 buckets #48
Labels
Milestone
Comments
|
This is an interesting idea, and I'd welcome a PR for that! |
|
agree! We have 8-12 accounts in AWS org and using independent buckets for state |
|
Could this be overcome by having multiple terraboard containers using the same PostgresDB? @kshcherban |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Could this issue be reopened? Terraboard is missing key feature |
|
Agreed. most terraform setups do not use a single state backend |
|
I was able to overcome this having a container for each account pointing them to same database and data was aggregated |
raphink
pushed a commit
that referenced
this issue
Jul 20, 2021
* feat: multi-provider support (WIP) * feat: env variables/flags available again for single provider configuration * feat: add some custom yaml unmarshalling rules to add default values where go-flags ones aren't applicable * docs: update readme with multiple buckets/providers config advices * feat: parallelized db refreshing and add mutex security + code review fixes from #177 * feat: add aws credentials & session token config support * allow aws multiple buckets to be configured directly in s3 yaml field (now an objects array) * add another minio instance to multiple-minio-buckets testing env * update all yaml example config files * docs: update readme with new aws configuration fields
|
fixed by #177 |
This was referenced Jul 31, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would be nice to have support for multiple s3 buckets for large terraform installations.
The text was updated successfully, but these errors were encountered: