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

[Server] Interpreting a View's filters by corresponding Design #10939

Open
leecalcote opened this issue May 13, 2024 · 2 comments
Open

[Server] Interpreting a View's filters by corresponding Design #10939

leecalcote opened this issue May 13, 2024 · 2 comments
Labels
component/server component/ui User Interface go Pull requests that update Go code issue/willfix This issue will be worked on kind/enhancement Improvement in current feature language/go Issues or pull requests that use Golang

Comments

@leecalcote
Copy link
Member

leecalcote commented May 13, 2024

This issue a child issue of the epic described in #10937. See the parent issue for additional context.

Current Behavior

Meshery UI users receive a some amount of information back from Meshery Server with depth of details varying based on type of event (operation performed).

For example, a successful design deployment might include a list of all components deployed, but might not be totaled by count or by which Kubernetes cluster to which they were deployed.

Desired Behavior

  1. Enhance Meshery Server events with aggregate metrics, summarizing the changes made:
    1. new components deployed
    2. existing components undeployed
    3. existing components updated
    4. total number of components implicated (by the design)
  2. Breakdown the change summary by Environment / by (K8s) Connection.
  3. For any design deployed, auto-generate a new View or include a reference to an existing View that is paired to the same design.

Implementation

Enhance the existing views api with a design ID query parameter such that the adjoining View doesn't need to be created, but that the design-specific filter (a set of filters configured to explicitly display only the resources included in the given design) is dynamically applied by the views API foregoing the need to create and track what essentially amounts to a foreign key between designs and views.

Acceptance Tests

Meshery Server clients (e.g. Meshery UI, mesheryctl, MeshMap) can GET a collection of discovered entities (resources) based constrained to those entities (i.e. components) defined in any given design.

Mockup

TBD


Contributor Guides and Handbook

@leecalcote leecalcote added kind/enhancement Improvement in current feature language/go Issues or pull requests that use Golang component/server go Pull requests that update Go code labels May 13, 2024
@leecalcote leecalcote added the component/ui User Interface label May 13, 2024
Copy link

This issue has been labeled with 'component/ui'. 🧰 Here are docs on Contributing to Meshery UI. 🎨 Here is the Meshery UI Figma File File. Lastly, here are docs on Contributing to Meshery's End-to-End Tests Using Cypress.


        Be sure to join the community, if you haven't yet and please leave a ⭐ star on the project 😄

@leecalcote
Copy link
Member Author

@MUzairS15 @aabidsofi19 FYI. The views API will need to be created first, however.

@leecalcote leecalcote added the issue/willfix This issue will be worked on label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/server component/ui User Interface go Pull requests that update Go code issue/willfix This issue will be worked on kind/enhancement Improvement in current feature language/go Issues or pull requests that use Golang
Projects
None yet
Development

No branches or pull requests

1 participant