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

data source: azurerm_subscriptions limited to 50 subscriptions #25219

Closed
1 task done
mgismaco opened this issue Mar 12, 2024 · 2 comments
Closed
1 task done

data source: azurerm_subscriptions limited to 50 subscriptions #25219

mgismaco opened this issue Mar 12, 2024 · 2 comments

Comments

@mgismaco
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • 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 and review the contribution guide to help.

Terraform Version

1.6.0

AzureRM Provider Version

3.9.4

Affected Resource(s)/Data Source(s)

azurerm_subscriptions

Terraform Configuration Files

data "azurerm_subscriptions" "available" {
}

output "name" {
  value = [ for sub in data.azurerm_subscriptions.available.subscriptions : sub.display_name ]
}

Debug Output/Panic Output

Changes to Outputs:
  + name = [
      + "Azure subscription 1",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx",
      + "sub-xxx"
      ]

Expected Behaviour

Data source should find ALL subscriptions

Actual Behaviour

Data source will not return more than 50 subscriptions.

Steps to Reproduce

No response

Important Factoids

No response

References

No response

@tombuildsstuff
Copy link
Contributor

hey @mgismaco

Thanks for opening this issue.

Taking a look through here this appears to be a duplicate of #24948 - rather than having multiple issues open tracking the same thing I'm going to close this one in favour of #24948, would you mind subscribing to that issue for updates?

Thanks!

Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants