-
Notifications
You must be signed in to change notification settings - Fork 25.4k
Update regions_by_endpoint for AWS sdk upgrade. #131400
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
Conversation
Also add test to ensure the file has at least one entry for each region so that it is easy to spot missing regions in future upgrades. Relates: elastic#131050
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
Label this as |
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.
Nice safeguard going forward!
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.
Hang on (I'll explain why in a sec)
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.
Actually hmm this is tricky.
The RegionFromEndpointGuesser
is there for bwc with the pre-8.19 behaviour in which you could omit the region, but my thinking was that brand-new regions don't need this bwc. Moreover if we try and keep the list up to date we'll have to keep on upgrading the AWS SDK rather more often than we would otherwise.
However on reflection I think we have to do this anyway because I suspect the v1 SDK will pick up these new regions automatically, so a user on 8.18 in the future may have working region-free config that won't work on upgrade to the v2 SDK unless we keep the v2 SDK up to date.
So, ok to proceed, but some concerns here about the implications.
Thanks for sharing the thoughts, David. Very helpful. I guess we probably can still call this best-effort to provide v1 users better upgrading experience, i.e. we strive to not break existing "region free" configs, but it may not be done continiously for every minor sdk version and the fallback (and actually the right solution) for users is to specify the region. |
@elasticmachine update branch |
The new attribute generated by MV_EXPAND should remain in the original position. The projection added by ProjectAwayColumns does not respect the original order of attributes. Make ProjectAwayColumns respect the order of attributes to fix this.
* ES|QL categorize options * refactor options * fix serialization * polish * add verfications * better test coverage + polish code * better test coverage + polish code
This PR migrates legacy rest tests in the x-pack autoscaling module
It's already part of the path parts, it's not useful to duplicate it in query parameters.
Also add test to ensure the file has at least one entry for each region so that it is easy to spot missing regions in future upgrades. Relates: elastic#131050 Resolves: elastic#131392
Also add test to ensure the file has at least one entry for each region so that it is easy to spot missing regions in future upgrades. Relates: #131050 Resolves: #131392 Co-authored-by: Elastic Machine <[email protected]>
Also add test to ensure the file has at least one entry for each region so that it is easy to spot missing regions in future upgrades.
Relates: #131050
Resolves: #131392