-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Databricks provider version #329
Conversation
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/UCLH-Foundry/FlowEHR/actions/runs/6240681607 (with refid (in response to this comment from @tanya-borisova) |
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/UCLH-Foundry/FlowEHR/actions/runs/6247966214 (with refid (in response to this comment from @jjgriff93) |
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/UCLH-Foundry/FlowEHR/actions/runs/6248597981 (with refid (in response to this comment from @jjgriff93) |
What is being addressed
Recent pull request #326 contains a bug: creation of databricks_metastore_assignment would sometimes error out with a message like "Storage credential XXX doesn't exist", and creation of metastore_data_access would also error out with a message like "No metastore assigned to the current workspace".
This has been fixed by upgrading the version of the provider to a newer one, and moving to account-level provider for these resources.
For more information, see databricks/terraform-provider-databricks#2182
Additional change I have made is now catalog name and schema name for Unity Catalog are passed in as Spark secrets, as opposed to pipeline inputs.