Enable feature flag 'validation.spatial.longitude.enableExtendedRange' for AWS

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

• [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• Google Cloud
• IBM

Does this introduce a breaking change?

• [NO]

What is the current behavior?

Without this feature, search can't handle the longitude outside the range [-180,180].

What is the new/expected behavior?

With this feature, search handle the longitude outside the range [-180,180].

Have you added/updated Unit Tests and Integration Tests?

Any other useful information

Related MR update os-core-common version in azure module to enable enableExtendedRange flag

changed milestone to %M23 - Release 0.26

added AWS MREnhancement labels

requested review from @ydzeng

assigned to @zhibinmai

@ydzeng please review it. If there is unit test failure, I will follow up.

@chad If AWS agrees, we should include this minor MR to M23.

approved this merge request

unapproved this merge request

requested review from @marcburnie

added 7 commits

• 69bbc89b...b79621be - 5 commits from branch master
• 2d5edd6c - Merge branch 'master' of https://community.opengroup.org/osdu/platform/system/search-service
• cf89e31b - Update integration tests

Compare with previous version

added 1 commit

• 75345bf6 - fixing aws integration test for extended longitude range

Compare with previous version

approved this merge request

resolved all threads

mentioned in commit 003bab0e

merged

picked the changes into the branch cherry-pick-003bab0e with commit 822db2a3

mentioned in commit 822db2a3

mentioned in merge request !643 (merged)

mentioned in merge request !725 (merged)