Please vote on this issue by adding a :thumbsup: 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
It looks like the random provider was pinned last year to 3.3.x. I'm guessing that this was due to the pending change between number and numeric. It appears that the code has been updated to use numeric, would it be possible to upgrade random or possibly remove the version pin?
I have other TF that I'm integrating this with that is using random 3.5 and it seems that the schema version has changed between 3.3 and 3.5.
Is there an existing issue for this?
Community Note
Description
It looks like the random provider was pinned last year to 3.3.x. I'm guessing that this was due to the pending change between number and numeric. It appears that the code has been updated to use numeric, would it be possible to upgrade random or possibly remove the version pin?
I have other TF that I'm integrating this with that is using random 3.5 and it seems that the schema version has changed between 3.3 and 3.5.
Thanks, Shane
New or Affected Resource(s
hashicorp/random
Potential Configuration file
No response
References
No response