Christopher T

I'm having the same issue now with: lnd version 0.7.0-beta commit=v0.7.0-beta-4-ga6e77811b1578f5d48191d0b9a5d4cbf895626f5 connect command failing: ``` $ lncli connect 0217890e3aad8d35bc054f43acc00084b25229ecff0ab68debd82883ad65ee8266@23.237.77.11:9735 [lncli] rpc error: code = Unknown desc = chain backend is...

Note that I found a fix for this issue and opened an issue in https://github.com/ElementsProject/lightning describing it: https://github.com/ElementsProject/lightning/issues/4848

Just saw this update... will try it thx!

I like @davidsteed's solution above... seems like the most robust BUT I don't understand why the latest version of the go sdk isn't _already_ incorporated into the container. (It's been...

This looks promising but not sure how to implement: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html

I am also having this problem when specifying glue partitions using `aws_glue_partition` although I'm not importing. I've not specified `additional_locations` anywhere in my config so not sure why it's thinking...

Furthermore, the docs for the aws_glue_partition resource don't show an additional location attribute nor will my TF validate if I add one :weary: https://registry.terraform.io/providers/-/aws/latest/docs/resources/glue_partition

The terraform lsp doesn't recognize the attribute either... it IS a property of `aws_glue_catalog_table` so why is it producing errors in the `aws_glue_partition` resource? 

The partition resources are tainted due to this error: ``` }, { "index_key": "2023-2", "status": "tainted", "schema_version": 0, "attributes": { "catalog_id": "012345678910", "creation_time": "2024-10-11T15:32:28Z", "database_name": "quicksight-usage", "id": "012345678910:usage:usage-cloudtrail:2023#2", "last_accessed_time": null,...

Still receiving this error in AWS Provider v5.80.0: ``` ╷ │ Error: setting storage_descriptor: Invalid address to set: []string{"storage_descriptor", "0", "additional_locations"} │ │ ```