-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
azurerm_data_factory_dataset_azure_sql_table - Table not set #25957
Comments
There's also an inconsistency as the azurerm_data_factory_dataset_sql_server_table uses "table_name" and does not have "schema" while azurerm_data_factory_dataset_azure_sql_table uses "table" and "schema"!? |
Another interesting thing I found... After deployment: After selecting the table from the dropdown: I don't do GoLang but I think maybe the azurerm_data_factory_dataset_azure_sql_table just sets the wrong thing (table and schema) and should configure tablename instead, like the azurerm_data_factory_dataset_sql_server_table does? |
This is still an issue. |
@Paxilein I had this same issue when trying to use the After applying the resource using the I added the column schema, applied it again, and this time it worked as expected. See if adding the column schema resolves the issue for you. Obs: the |
Is there an existing issue for this?
Community Note
Terraform Version
1.8.1
AzureRM Provider Version
3.103.1
Affected Resource(s)/Data Source(s)
azurerm_data_factory_dataset_azure_sql_table
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The dataset should have the table "foo" configured in ADF, like it does when using the azurerm_data_factory_dataset_sql_server_table
Actual Behaviour
The table field in ADF Studio shows "Select..." and the "Enter manually" is disabled. We have to manually select a table before it works...
Maybe the manual field isn't configured to be set in this resource when the table is specified?
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: