Daniel (dB.) Doubrovkine

> @dblock This was encountered for the Alerting OpenSearch repo. We don't have insight into the branch protection rules in the `Settings` but after I pushed the dev branch `bucket-level-alerting-dev`...

> it prevented any subsequent commits because the branch was marked as "protected" @qreshi Branch protection just says that you need to be doing PRs into the branch and not...

This really belongs in https://github.com/opensearch-project/.github, moving the issue there.

A few ideas. 1. Explain that maintaining licenses and thirdparty licenses is maintainer responsibilities in https://github.com/opensearch-project/.github/blob/main/MAINTAINERS.md. 2. Document specifics for OpenSearch plugins in https://github.com/opensearch-project/opensearch-plugins/, some in https://github.com/opensearch-project/opensearch-plugins/blob/main/HEADERS.md Note that the...

The spec is pretty far from passing dredd, but I'll keep chipping at it. @Xtansia @nhtruong LMK what you think about this approach?

This is ready to review @Xtansia @nhtruong. Leaving as draft so I can add at least some tests for HEAD/PUT/POST before adopting dredd.

> @dblock I've added some suggestions on how to do the filtering without in-place deletes, also avoids the assumption that all properties of a path object are http methods, there...

@nhtruong I added POST and DELETE specs, which required correcting the response code from POST to be 201, but now the linter complains that the responses for all `index` should...

Note that https://localhost:9200/_cat?format=json doesn't return JSON. AFAIK there's no way in OpenAPI to say parameter X -> this kind of output, or is there?

This was fixed in https://github.com/opensearch-project/opensearch-api-specification/pull/360 and https://github.com/opensearch-project/opensearch-api-specification/pull/357.