Repository navigation
Fix OpenSearch readiness for alternative field mappings - #139
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why This Change Is Needed
The deployed dev API returned
503 SEARCH_NOT_READYeven while normal/searchrequests succeeded. A task-local_field_capsdiagnostic confirmed that OpenSearch was reachable but six optional physical fields were unmapped. The previous validator required every possible field path, so one absent CNA, ADP, legacy, or CVSS variant made the entire API unready.The Postman
Readiness returns 200expectation remains correct. Readiness should confirm that each logical search feature has a compatible mapped implementation, not require every optional storage variant to exist.Primary Files
utils/searchReadiness.js: models logical capability groups and validates compatible alternatives.utils/searchReadiness.test.js: covers missing groups, unmapped alternatives, incompatible mapped fields, and the exact dev regression.routes/index.js: updates generated readiness endpoint documentation.api-docs/openapi.json: updates the published readiness description.README.md: documents grouped readiness behavior.