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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
When creating multiple AD Groups simultaneously, there are intermittent errors where the "id" property does not become available on the resource. This is easiest to reproduce when AD Groups are created within a module.
I'm currently working around this by adding dependencies to throttle the AD group creation, but this appears to be an issue unless I'm missing something.
Two AD groups created for each instance of the module.
Actual Behavior
Intermittently errors on some AD Groups with an error of: Resource 'azuread_group.two' does not have attribute 'id' for variable 'azuread_group.two.id'
or Resource 'azuread_group.one' does not have attribute 'id' for variable 'azuread_group.one.id'.
Errors begin to appear when creating 8+ AD Groups simultaneously.
Steps to Reproduce
Create an empty directory
Place the module code above into /module/main.tf
Place the main.tf code at the root directory
terraform init
terraform apply
The text was updated successfully, but these errors were encountered:
katbyte
changed the title
azuread_group ID does not become available when creating multiple groups simultaneously (intermittent).
azuread_group ID: does not become available when creating multiple groups simultaneously (intermittent).
May 23, 2019
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.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Jul 5, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
When creating multiple AD Groups simultaneously, there are intermittent errors where the "id" property does not become available on the resource. This is easiest to reproduce when AD Groups are created within a module.
I'm currently working around this by adding dependencies to throttle the AD group creation, but this appears to be an issue unless I'm missing something.
Terraform (and AzureAD Provider) Version
Terraform v0.11.13
provider.azuread v0.2.0
Affected Resource(s)
azuread_group
Terraform Configuration Files
Debug Output
https://gist.github.com/TonyLunt/9f30ebf4cbdd4c835c4757d9548b48d5
Expected Behavior
Two AD groups created for each instance of the module.
Actual Behavior
Intermittently errors on some AD Groups with an error of:
Resource 'azuread_group.two' does not have attribute 'id' for variable 'azuread_group.two.id'
or
Resource 'azuread_group.one' does not have attribute 'id' for variable 'azuread_group.one.id'
.Errors begin to appear when creating 8+ AD Groups simultaneously.
Steps to Reproduce
terraform init
terraform apply
The text was updated successfully, but these errors were encountered: