8000 reading Azure ad group members causes memory spike and crash => data "azuread_group" "example" · Issue #1612 · hashicorp/terraform-provider-azuread · GitHub
[go: up one dir, main page]

Skip to content
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

reading Azure ad group members causes memory spike and crash => data "azuread_group" "example" #1612

Open
Sharmanand opened this issue Jan 8, 2025 · 4 comments

Comments

@Sharmanand
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritise this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritise the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureAD Provider) Version

Terraform Version 1.9.6
provider registry.terraform.io/hashicorp/azuread v3.0.2

Affected Resource(s)

  • data.azuread_group.example

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp

Debug Output

Panic Output

Expected Behavior

We have several groups managed by terraform. However after upgrading to v.3.02 it's taking time retrieve the group and using insane amount of memory.

Actual Behavior

Steps to Reproduce

  1. terraform plan

Important Factoids

References

  • #0000
@Sharmanand
Copy link
Author

@mbfrahry can you please review?

@manicminer
Copy link
Contributor

@Sharmanand Are you sure you're using 3.0.2? This was fixed in that version (3.0.0 and 3.0.1 exhibit this issue).

@Sharmanand
Copy link
Author

@manicminer yes i tried with v3.0.2. terraform plan also taking significant amount of time. v.2.5.3 was all good i tested against.

@Sharmanand
Copy link
Author
Sharmanand commented Jan 12, 2025

5FF5 @manicminer @mbfrahry fyi. i checked last commit and feel that they only fixed ad group resource (resource "azuread_group" "example") and issue still exist for ad group data resource(data "azuread_group" "example")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0