Niko

As far as I know, deltalake expects all the AWS parameters to be defined in the environment, exactly as you noted @Shershebnev. `~/.aws/*` files on Linux/Mac are managed by AWS...

Yes @ion-elgreco, looks like Polars is using the second approach I mentioned - looking into specific files config and credentials files it "knows" may exist. However, it uses hard-code paths...

It looks like the current implementation works for storage location retrieval, but will require additional creds for data access. (in addition to Azure I also tried in AWS - similar...

Actually, this looks like an expected behavior, mentioned in https://github.com/delta-io/delta-rs/pull/1331#issuecomment-1581557227

@rtyler maybe you could include me in those future conversations given I work for Databricks atm :grin

Thank you, go for it @micheledaddetta-databricks, I think @alexott can assign this to you

Hey @alexott, I can take this

List of examples to convert: - [x] adb-exfiltration-protection - [x] adb-external-hive-metastore - [x] adb-kafka - [x] adb-lakehouse - [ ] ***postponed***adb-overwatch: subject to outcome of #159 - [x] adb-private-links -...

I did not make any changes to `network_security_group_rules_required` as mentioned in [azurerm_databricks_workspace](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/4.0-upgrade-guide#azurerm_databricks_workspace). Testing a deployment with it added to `ignore_changes` resulted in a failing `destroy` so I didn't do it...

Agree with this example loosing it's relevance Also, module `adb-overwatch-main-ws` doesn't have anything specific to Overwatch - just a regular workspace