-
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_linked_service_data_lake_storage_gen2 use_managed_identity false doesn't setup a working connection #11591
Comments
@jwshive accoridng to doc: https://docs.microsoft.com/en-us/azure/data-factory/connector-azure-data-lake-storage#managed-identity If you want to use managed Identity authentication, you should assign the relevant roles. For example:
Then I believe you could get the successfully connection. If you want to use the account key authentication, PR #12136 has add support for it. You could upgrade to the latest version and have a try! |
I don't know that I can use the latest version. We run all of our code through azure devops and I can't get it to init on any version above 0.14.11. That said, I still don't feel like this is working properly. To "fix" my issue I just have to toggle it off and back on again. So the code doesn't seem to be the problem. |
@jwshive What I mean is there are different ways to do it:
|
Closing this out since this appears to be resolved? |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
on darwin_amd64
Terraform Configuration Files
Debug Output
Panic Output
Expected Behaviour
I expect I should be able to test the connection and it connects successfully to adlsgen2
Actual Behaviour
Connection fails with
Steps to Reproduce
terraform destroy on the linked service
terraform apply
Important Factoids
On the linked service settings pane, the host is the correct url and the account key is populated.
If I change the account selection method from manual to 'from azure subscription' and select the same storage account, I see it briefly say loading key and then I can test and get a successful connection.
When I go back into the settings pane, the url is exactly the same and the account key is populated, but I cannot see what the actual account key is.
I'm assuming it's getting the wrong account key from somewhere, but I'm not sure where that would be or how I can provide it the correct key.
When I do the above and get a successful connection, I am able to run a terraform plan again on the unaltered code and there are no changes detected.
References
The text was updated successfully, but these errors were encountered: