Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rules & capability schemas #311

Closed
3 tasks done
pranavgaikwad opened this issue Aug 31, 2023 · 4 comments
Closed
3 tasks done

Rules & capability schemas #311

pranavgaikwad opened this issue Aug 31, 2023 · 4 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@pranavgaikwad
Copy link
Contributor

pranavgaikwad commented Aug 31, 2023

At some point, we should be generating an openapi spec for rules schema. We need mainly two things:

  • Providers need to return a schema for their capabilities
  • The engine needs to consolidate built-in conditions schemas and capability schemas into a rules schema, and validate the input rules against it

And finally we probably want another command that generates a JSON spec.

Tasks

Preview Give feedback
  1. kind/feature priority/important-soon triage/accepted
@pranavgaikwad pranavgaikwad added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Aug 31, 2023
@pranavgaikwad pranavgaikwad moved this to 📋 Backlog in Planning Jan 25, 2024
@pranavgaikwad pranavgaikwad added this to the v0.4.0 milestone Jan 25, 2024
@pranavgaikwad
Copy link
Contributor Author

We need an enhancement to discuss how this will be delivered to the end user.

@shawn-hurley
Copy link
Contributor

Some ideas that I have:

  1. Something akin to the old Godoc command that would run a local Godoc server based on the project and the deps.
  2. A quick way to run a given rule file against the schemas (kantra rule schema-test) or something of the sort
  3. Should be integrated into the rule testing enhancement as well

Please take these and either ignore them or make them better. They were very rough thoughts :)

@shawn-hurley shawn-hurley self-assigned this Feb 12, 2024
@konveyor-ci-bot konveyor-ci-bot bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 7, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. label Mar 7, 2024
@shawn-hurley shawn-hurley moved this from 📋 Backlog to 🏗 In progress in Planning Mar 7, 2024
@shawn-hurley shawn-hurley added kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Mar 7, 2024
@konveyor-ci-bot konveyor-ci-bot bot removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. labels Mar 7, 2024
@shawn-hurley
Copy link
Contributor

This has been completed all tasks are finished

@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Planning Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants