You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any waiter with a jmespath comparison expression using <, <=, >, or >= is broken, because ordered comparison in go-jmespath itself appears to be broken:
The following service models contain affected paths: cloudwatch, ec2, and auto-scaling. Fortunately EC2 is not actually broken because we previously migrated this to generated waiters.
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Any waiter with a jmespath comparison expression using <, <=, >, or >= is broken, because ordered comparison in
go-jmespath
itself appears to be broken:The following service models contain affected paths: cloudwatch, ec2, and auto-scaling. Fortunately EC2 is not actually broken because we previously migrated this to generated waiters.
This means that these waiters in cloudwatch and autoscaling are still broken today.
Fortunately we do have a path forward here in migrating to generated waiters. See #2977.
The text was updated successfully, but these errors were encountered: