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

API error when managing users "Requested range order is not allowed" #379

Closed
leetrout opened this issue Oct 10, 2023 · 4 comments · Fixed by #380
Closed

API error when managing users "Requested range order is not allowed" #379

leetrout opened this issue Oct 10, 2023 · 4 comments · Fixed by #380

Comments

@leetrout
Copy link

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

Terraform v1.5.5
on darwin_amd64
+ provider registry.terraform.io/heroku/heroku v5.2.6

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

Error: Get "https://api.heroku.com/teams/apps/<UUID>/collaborators": Requested range order is not allowed, please try `id` or another specified in `Accept-Ranges`.

Steps to Reproduce

  1. terraform apply
@mars
Copy link
Member

mars commented Oct 11, 2023

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 v5.2.7-pre.1 with the proposed fix #380. Please help me validate it by specifying provider:

terraform {
  required_providers {
    heroku = {
      source = "heroku/heroku"
      version = "5.2.7-pre.1"
    }
  }
}

I'll release v5.2.7 once our peer review is complete, and hopefully you confirm success 🙏

@mars mars closed this as completed in #380 Oct 11, 2023
@mars
Copy link
Member

mars commented Oct 11, 2023

This is fixed in v5.2.7. Use with:

terraform {
  required_providers {
    heroku = {
      source = "heroku/heroku"
      version = "5.2.7"
    }
  }
}

@leetrout
Copy link
Author

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 😞

@leetrout
Copy link
Author

We hit the bug again today on 5.2.6 and confirming upgrading to 5.2.7 fixed it.

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

Successfully merging a pull request may close this issue.

2 participants