-
Notifications
You must be signed in to change notification settings - Fork 77
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
API error when managing users "Requested range order is not allowed" #379
Comments
Thanks for letting us know @leetrout 😃 It seems to require a simple fix, which I proofed using curl HTTP requests to Heroku API. I've made pre-release terraform {
required_providers {
heroku = {
source = "heroku/heroku"
version = "5.2.7-pre.1"
}
}
} I'll release |
This is fixed in terraform {
required_providers {
heroku = {
source = "heroku/heroku"
version = "5.2.7"
}
}
} |
Thank you @mars! We found a work-around yesterday by removing some users manually and re-adding them so I don't have the same state to test with 😞 |
We hit the bug again today on 5.2.6 and confirming upgrading to 5.2.7 fixed it. |
Terraform Version
Run
terraform -v
to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.Heroku Provider Version
Affected Resource(s)
Please list the resources as a list, for example:
heroku_team_collaborator
Terraform Configuration Files
We cannot share - it is a list of 36
heroku_team_collaborator
resources.Debug Output
We cannot provide the debug output due to privacy issues.
Expected Behavior
Terraform applies cleanly
Actual Behavior
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: