While I'd still like to have it all in aws-vault (some setups use SAML, some OID, some AWS SSO, some plain credentials), I do see the point of not making it extra complicated...

If it really is unreasonably hard to get this integrated I should probably see if the reverse can be done -- hooking a frontend up to a SAML client as well as having aws-vault as a client. It would still give the best of both worlds (somewhat).

Very cool to see this get picket up fast! We'll be using it as soon as it's released so if it doesn't work as intended we'll know relatively quickly.

I'm running in to the same thing with W60B and T57W firmwares, both use UBIFS as well (and encrypted too). Did you ever find a way to decrypt those filesystems @electroniceel ?

It was just simple struct generation from kaitai.

I looks like there is a missing module, it doesn't seem to be published anywhere either. Is this because it needs to be generated from Kaitai?

I looks like there is a missing module, it doesn't seem to be published anywhere either.

Tested by: me

Does what is says on the tin

I'm using this data (for host identity machine with other data sources that only supply a MAC address), but as already commented and mentioned this can be done using a separate query just fine.

Does it sill work on python 2? (I haven't had time to run tests myself, sorry)

<!--- Please note the following potential times when an issue might be in Terraform core:

• Configuration Language or resource ordering issues
• State and State Backend issues
• Provisioner issues
• Registry issues
• Spans resources across multiple providers

If you are running into one of these scenarios, we recommend opening an issue in the Terraform core repository instead. --->

<!--- Please keep this note for the community --->

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

<!--- Thank you for keeping this note for the community --->

Terraform Version

Terraform v0.12.21

• provider.aws v2.69.0
• provider.cloudflare v2.8.0
• provider.template v2.1.2

Affected Resource(s)

• aws_s3_bucket_object

Terraform Configuration Files

data "aws_s3_bucket_object" "placeholder" {
  bucket = "some_bucket_name"
  key    = "/" 
}

Debug Output

https://gist.github.com/johnkeates/6f16cce6357fa1c20c16c9077939b996

Expected Behavior

An error should have been shown

Actual Behavior

The provider crashed

Steps to Reproduce

1. Create this:

data "aws_s3_bucket_object" "placeholder" {
  bucket = "some_bucket_name"
  key    = "/" 
}

2. terraform apply