-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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_client_config not returning object_id expected "access_policy.0.object_id" to be a valid UUID #17039
Comments
Hitting what I strongly suspect is the same issue. Same error message trying to use the value Edit: I stand corrected. I don't understand the cause, but while trying to track down the source of the problem, I was able to reproduce the OP's issue where the Edit 2: damit, microsoft. the If I replace
|
I'm seeing this from tf1.2.1 on macOS:
|
…ent.client_id issue is fixed (hashicorp/terraform-provider-azurerm#17039)
same here after updating provider from 2.99 to 3.8.0 with latest terraform 1.2.1. |
I am having this issue in a new project. I am running 1.2.2. this is the output I am seeing:
This also happens in tf 1.1.3. |
Duplicate of #16982 - this is a breaking change within the Azure CLI. |
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. |
Is there an existing issue for this?
Community Note
Terraform Version
1.0.3
AzureRM Provider Version
3.8.0
Affected Resource(s)/Data Source(s)
azurerm_client_config
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
object_id should be populated with the proper ID
Actual Behaviour
object_id is not present in state show
data "azurerm_client_config" "current" {
client_id = "04b07795-8ddb-461a-bbee-xxxxxxxxxxxxx"
id = "2022-05-31 18:08:40.380213 +0000 UTC"
subscription_id = "90376dc6-e4a0-49c3-930d-xxxxxxxxxxxxx"
tenant_id = "fb3a99b4-c0f5-4c61-9f05-xxxxxxxxxxxxx"
}
Steps to Reproduce
terraform apply using the azurerm_client_config should easily repro
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: