You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you so much for building the Terraform registry modules. I am facing some issues with the modules when I use the below terraform.tfvars. I have Contributor rights on the AD App and I am running below command to Auth before running TF Apply. All the resources are getting created but it leaves me with below error messages. Not sure if the deployment has completed or not.
az login --service-principal -u "ae83018d-d8d7-4198-a10f-6187ba1daec1" -p "xyz" --tenant "9f37a392-f0ae-4280-9796-f1864a10effc"
Even though all the resources get deployed in Azure subscription. I still see below errors.
(url)
Am I missing some configuration? or some Role permissions?
Am I supposed to use a separate storage account name for an external location?
The text was updated successfully, but these errors were encountered:
@suneelsunkara-db I did manage to get it to deploy but continued to have an error with the external data account. I am certainly not a terraform expert, but it seems some of the dependencies may be off and cause the errors. From my testing, the deployment does appear to work across the metastore and other azure resources.
Thank you so much for building the Terraform registry modules. I am facing some issues with the modules when I use the below terraform.tfvars. I have Contributor rights on the AD App and I am running below command to Auth before running TF Apply. All the resources are getting created but it leaves me with below error messages. Not sure if the deployment has completed or not.
az login --service-principal -u "ae83018d-d8d7-4198-a10f-6187ba1daec1" -p "xyz" --tenant "9f37a392-f0ae-4280-9796-f1864a10effc"
Even though all the resources get deployed in Azure subscription. I still see below errors.
(url)Am I missing some configuration? or some Role permissions?
Am I supposed to use a separate storage account name for an external location?
The text was updated successfully, but these errors were encountered: