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.

Sign up for GitHub

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

Jump to bottom

New Schema: Policy #204

Open
leecalcote opened this issue Jan 1, 2025 · 0 comments
Open

New Schema: Policy #204

leecalcote opened this issue Jan 1, 2025 · 0 comments
Labels
issue/willfix This issue will be worked on kind/child One of a number of issues relating to an epic kind/enhancement Improvement in current feature

Comments

@leecalcote
Copy link
Member

leecalcote commented Jan 1, 2025 •
edited
Loading

This is a child issue. See the parent issue for additional details: meshery/meshery#13059

Current Behavior

Meshery has support for policies, which need to be schema-driven.

Desired Behavior

Consequently, Meshery will need a Policy schema formally defined.

Implementation

Endpoints to be supported:

  1. /api/meshmodels/models/{model}/policies | Returns full defintion of a specific entity for the latest version
  2. /api/meshmodels/models/{model}/policies/{policy} | Returns a list of registered policies within model scope

Acceptance Tests

Design spec needed

Mockups

Contributor Guides and Handbook
@leecalcote leecalcote added issue/willfix This issue will be worked on kind/enhancement Improvement in current feature labels Jan 1, 2025
@leecalcote leecalcote mentioned this issue Jan 1, 2025
Open
6 tasks
@leecalcote leecalcote added the kind/child One of a number of issues relating to an epic label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
issue/willfix This issue will be worked on kind/child One of a number of issues relating to an epic kind/enhancement Improvement in current feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@leecalcote