ParthaI
commented
3 months ago Hi @keyolk,
I apologize for the delayed response.
Here are a few key points for you to review:
- This plugin supports searching Terraform resources from an S3 bucket.
- Have you had a chance to look at the plugin documentation?
- I tested it locally with
.tffile resources stored in an S3 bucket, and I got the expected results using the following configuration in theterraform.spcfile:
connection "tf_bucket" {
plugin = "terraform"
configuration_file_paths = [
"s3::https://test-delete90.s3.us-east-2.amazonaws.com//**/*.tf?aws_profile=default"
]
}Query Result:
> select * from tf_bucket.terraform_resource
+---------------------+----------------------+--------+-----------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
| name | type | mode | address | arguments >
+---------------------+----------------------+--------+-----------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
| example | tls_private_key | <null> | tls_private_key.example | {"algorithm":"RSA"} >
| | | | | >
| | | | | >
| named_test_resource | aws_acm_certificate | <null> | aws_acm_certificate.named_test_resource | {"certificate_body":"${tls_self_signed_cert.example.cert_pem}","private_key":"${tls_private_key.example.private_key_pem}","tags":{"name":"turbot-test-20200125-create-update"}} >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| example | tls_self_signed_cert | <null> | tls_self_signed_cert.example | {"allowed_uses":["key_encipherment","digital_signature","server_auth"],"private_key_pem":"${tls_private_key.example.private_key_pem}","subject":{"common_name":"turbot.com","organization":"Turbot HQ Pvt. Ltd."},"valid>
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
| | | | | >
+---------------------+----------------------+--------+-----------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->I haven’t yet tried it with a tfstate file in an S3 bucket. Could you please give it a try and let us know if you encounter any further issues?
Thank you!
keyolk
I am testing steampipe against tfstates. I am managing multiple tfstate files in one s3 bucket. After testing, it seems that formats such as "$bucketname/*/.tfstate" are not supported. In practice, we manage a lot of tfstates, and it would be very helpful if recursive search is possible.
Found some test cases which looks related to this https://github.com/turbot/steampipe-plugin-sdk/blob/develop/plugin/get_source_files_test.go#L165 But it never work as I expected