Daniel Widdis

Previous issue linked to https://github.com/opensearch-project/security/issues/3771 which was supposed to have been fixed, but there's at least one other report of this error in 2.14 here: https://github.com/opensearch-project/security/issues/3771#issuecomment-2136941571 CC: @cwperks

Possibly is related to https://github.com/opensearch-project/performance-analyzer/issues/606 Still-open PR to fix: https://github.com/opensearch-project/performance-analyzer/pull/609

> Do dependent plugins like ml-commons/flow framework need to do anything based on this change? The only change upstream is aligning bom version with OpenSearch which is getting version bumps...

Note the setup (linked above) to flow-framework will replace _all_ headers in all files. You'll need to add some exclusions to files which have custom headers, for example [files in...

> > * it "pollutes" the spec with cloud vendor details (I can easily imagine such list offerings to grow unbound) > > I suppose I wouldn't be against it!...

> We can move these annotations from the spec into some yaml that doesn't have to live in this repo (eventually), which I think would satisfy all the concerns above....

> These YAML files list API test cases, which the smoke test workflow executes. The results are then validated against the OpenSearch API Specification to ensure API correctness and expected...

> Onboarding to this framework will provide more efficient and comprehensive sanity testing across all release artifacts Thanks, @zelinh. I understand the intent to have at least some basic API...

Thanks for the clarification!

Pending: - [x] https://github.com/opensearch-project/opensearch-remote-metadata-sdk/pull/172 - [x] https://github.com/opensearch-project/common-utils/pull/826 - [x] https://github.com/opensearch-project/ml-commons/pull/3830 - [x] https://github.com/opensearch-project/k-NN/pull/2695 - [x] https://github.com/opensearch-project/neural-search/pull/1306