-
Notifications
You must be signed in to change notification settings - Fork 19
Description
🚀 Feature description
Great to get the ability to deploy a fabric_sql_database but to make it useful to downstream terraform config it would be great if it returned the connection details for the created database (similar to how fabric_warehouse does).
Something like below in the state maybe
"instances": [
{
"schema_version": 0,
"attributes": {
"description": "example",
"display_name": "sql_example",
"id": "f852eea4-e36c-4590-8b36-20569cae7fb8",
"timeouts": null,
"workspace_id": "c4ddf736-752f-4a03-8970-399d969d4c4a",
"properties": {
"server_fqdn": "dqjx2zrgh4uejnetrut54cdkau-g3353rbpoubuvclqhgoznhkmji.database.fabric.microsoft.com",
"database_name": "sql_example-f852eea4-e36c-4590-8b36-20569cae7fb8"
},
},
"sensitive_attributes": []
}
]🔈 Motivation
In order by create downstream terraform config eg, add connection details to key vault we need the fabric_sql_database create to return to server_fqdn & the database_name
🛰 Alternatives
We can get:
database_name via a concat of display_name and id
server_fqdn via a warehouse create output and swapping .datawarehouse.fabric.microsoft.com with .database.fabric.microsoft.com
Neither are ideal though
🚧 Potential Configuration / Desired Solution
Output similar to below
"instances": [
{
"schema_version": 0,
"attributes": {
"description": "example",
"display_name": "sql_example",
"id": "f852eea4-e36c-4590-8b36-20569cae7fb8",
"timeouts": null,
"workspace_id": "c4ddf736-752f-4a03-8970-399d969d4c4a",
"properties": {
"server_fqdn": "dqjx2zrgh4uejnetrut54cdkau-g3353rbpoubuvclqhgoznhkmji.database.fabric.microsoft.com",
"database_name": "sql_example-f852eea4-e36c-4590-8b36-20569cae7fb8"
},
},
"sensitive_attributes": []
}
]📎 Additional context
No response
☑️ Acceptance Criteria
Once a fabric_sql_database is deployed we can get its server_fqdn & database_name
🔰 Code of Conduct
- I agree to follow this project's Code of Conduct.