Remove schema.json and the code that generates it

[webmat]

This file is no longer used to power the SIEM field browser.

[ruflin]

We should be careful to remove such file as I would argue if someone else uses these, it is a breaking change. Not to the schema, but to our tooling.

[webmat]

Its creator didn't even end up using it 🤷‍♂

[ruflin]

🤦‍♂ That doesn't mean someone else is using it. I'm good with this "breaking change" but lets at least have it in the changelog so users know.

[webmat]

Yeah, someone else may be using it.

If anyone needs this, please make yourselves heard, even if this PR has already been merged. We can bring it back if needed :-)

[webmat]

• Move this changelog entry to "tooling" after Split changelog in two sections #633

[pete-otaqui-sky]

Hi - I'd like to ask for this to be put back in. We'd like to be able to validate ECS compatibility using AWS API Gateway, which depends on JSON Schema. Would you like a PR for putting it back?

[ebeahan]

Hi @pete-otaqui-sky. Currently ECS doesn't maintain a JSON format of the schema as part of the generated artifacts. However, the ecs_nested.yml file is intended to be consumed programmatically and YAML can be painlessly converted to a JSON format if required for your needs.

Please feel free to open a new issue if you'd like to discuss further or have additional questions.