-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
numeric comparisons for versions #20383
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @brenthc 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTING guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
@ewbankkit Hi I'm not sure if this 100% working on a non BUILD lex bot which has only $LATEST and no version. I see nowhere where $LATEST will be returned. This code has a significant issue as the old code could have returned > 1 or $LATEST. this code on the other hand now returns > 0 which would not be expected by existing state. You need something like I have in my closed PR like this
|
@thornleyk Thanks - Yes I did correct that in the merged version. @brenthc Thanks for the contribution 🎉 👏. I have incorporated these changes into #21122. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #21045.
Not sure about adding tests for this, as it'd be necessary to create more than 9 versions so that numeric vs lexical sorting can be verified.