Daniel (dB.) Doubrovkine

IMO it's still a valid request, but I personally don't have a scenario where I need latest for a 1.x build, so wouldn't have a heartburn over the ask being...

[Catch All Triage - Attendees [1](https://github.com/dblock/), [2](https://github.com/krisfreedain), [3](https://github.com/andrross), [4](https://github.com/gkamat), [5](https://github.com/getsaurabh02)]

When I introduced this feature in https://github.com/opensearch-project/opensearch-api-specification/pull/510 I did not intend it to be biased towards supporting AWS in any way, but I did want to run the tests against...

> * 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! As a positive,...

> TLDR: We need a way for an app/front-end to query the spec (filtered by ) to know whether to display options on it's UI. I don't know if that's...

No backport to 2.x?

[Catch All Triage - Attendees [1](https://github.com/dblock/), [2](https://github.com/krisfreedain), [3](https://github.com/andrross), [4](https://github.com/gkamat), [5](https://github.com/getsaurabh02)]

@ransel AFAIK nobody is working on it, want to help? I'd start by ensuring this feature exists in the [API spec](https://github.com/opensearch-project/opensearch-api-specification/).

[[Catch All Triage](https://github.com/opensearch-project/.github/blob/main/TRIAGING.md) - [1](https://github.com/dblock), [2](https://github.com/andrross/), [3](https://github.com/reta), [4](https://github.com/gaiksaya), [5](https://github.com/krisfreedain), [6](https://github.com/acarbonetto)]

[[Catch All Triage](https://github.com/opensearch-project/.github/blob/main/TRIAGING.md) - [1](https://github.com/dblock), [2](https://github.com/andrross/), [3](https://github.com/reta)]