[Server] Enhance information for the events sent by server.

[MUzairS15]

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

For design save events:

1. Include no of components,
2. Size,
3. Link to design
4. Link to view
5. .... other?

Implementation

See child issues:

• 1. [UI] Metadata Formatter for Deploy / Undeploy Events #10946
• 2. [Server] New views API #10943
• 3. [Server] Interpreting a View's filters by corresponding Design #10939
• 4. need new issue created for the "Views" page in Meshery UI

Acceptance Tests

See the child issues.

Mockups

See the child issues.

---

Contributor Guides and Handbook

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

[leecalcote]

@aabidsofi19 @MUzairS15 regarding #3 above, in the short-term, I'll suggest that the best approach here is one of enhancing 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. I do think that Meshery will eventually take this step with a 1:1 implicitly-generated relationship between Design and View (such that a Design doesn't exist without a View - while the inverse may not be true), however, I'll content that it's a step too far in the current release train.

[github-actions]

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 😄