Replies: 1 comment
-
Hi @tenzone Please see documentation below- Resource structure The default path for resource files is {output}/{provider}/{service}/{resource}.tf and can vary for each provider. It's possible to adjust the generated structure by: Using --compact parameter to group resource files within a single service into one resources.tf file |
Beta Was this translation helpful? Give feedback.
-
My intended use case, in aws, is to tag resources related to a project with
"Project":"PROJECT_NAME"
. I would like to scan AWS account and apply a filter to match on that tag using--filter="Name=tags.project;Value=PROJECT_NAME"
. This works in general, but it creates a state file for all the different resource groups, where i would rather them all be in the same state file, as they should be logically grouped anyhow. Is there a way to fo this?EDIT: i think i did not read the docs too well, as it looks like I can use the putput path to achieve this...
Beta Was this translation helpful? Give feedback.
All reactions