falcoSchema.json should be generated by Falco itself

[leogr]

Motivation

Falco should be responsible for defining its supported rule syntax schema. Other tools can consume the schema, then.

For projects like falco-project, consuming this schema in JSON format is very useful. The project is currently using a static version of it https://github.com/falcosecurity/falco-playground/blob/main/src/components/Editor/falcoSchema.json

Feature

Make Falco generate the rule syntax schema in JSON format.

Alternatives

Additional context

Initially, I've filled this issue under the falco-playground project since we have a live example of what we need. The end goal is to transfer this issue to the falco repository and implement the feature in Falco.

I'm assigning this issue to me, but I need volunteers to help. 🙏
/assign
/help

cc @falcosecurity/core-maintainers @falcosecurity/falco-playground-maintainers

[poiana]

@leogr:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

Motivation

Falco should be responsible for defining its supported rule syntax schema. Other tools can consume the schema, then.

For projects like falco-project, consuming this schema in JSON format is very useful. The project is currently using a static version of it https://github.com/falcosecurity/falco-playground/blob/main/src/components/Editor/falcoSchema.json

Feature

Make Falco generate the rule syntax schema in JSON format.

Alternatives

Additional context

I've filled this issue under the falco-playground project since we have a live example of what we need. The end goal is to transfer this issue to the falco repository and implement the feature in Falco.

I'm assigning this issue to me, but I need volunteers to help. 🙏
/assign
/help

cc @falcosecurity/core-maintainers @falcosecurity/falco-playground-maintainers

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale

cc @falcosecurity/falco-maintainers, I really believe we should move that file to the Falco repo. Do you agree?

also, @LucaGuerra, may that file need to be aligned with #2981?

cc @Rohith-Raju

[Rohith-Raju]

@leogr Yes, I agree!!
Maybe we could add an additional flag where Falco outputs the schema in Json format

[leogr]

We are doing a similar thing for Falco config files. I believe it's time to revamp this. I'm transferring the issue to the falco repo.

[leogr]

/kind feature

Proposing
/milestone 0.38.0
cc @falcosecurity/falco-maintainers

If anyone is willing to help, please let me know. 🙏

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[FedeDP]

/remove-lifecycle stale

[FedeDP]

Implemented in #3313.