This issue has been labeled with 'component/mesheryctl'. Note that after making changes you need to update it in the mesheryctl command tracker spreadsheet.

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

This issue has been labeled with 'design-required'. Note that prior to commencing on implementation, a design specification needs to be created and reviewed for approval. See Creating a Functional Specification to create a design spec.

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

@alphaX86 Sir, I'm contemplating introducing list and view as subcommands, similar to exp model and exp components, after reviewing the schema of relationships. Here's an example snippet:

{
  "kind": "Edge",
  "apiVersion": "core.meshery.io/v1alpha1",
  "model": {
    "name": "kubernetes",
    "version": "v1.25.2",
    "displayName": "Kubernetes",
    "hostname": "",
    "hostID": "00000000-0000-0000-0000-000000000000",
    "displayhostname": "",
    "category": {
      "name": "",
      "metadata": null
    },
    "metadata": {},
    "components": [],
    "relationships": []
  },
  "hostname": "artifacthub",
  "hostID": "9a672bbb-51a1-5586-8dfc-75013445eebb",
  "displayhostname": "Artifacthub",
  "metadata": {
    "description": "A relationship that acts as a firewall for ingress and egress traffic from Pods."
  },
  "subType": "Firewall",
  "rego_query": "edge_binding_relationship",
  "selectors": {
    "allow": {
      "from": [
        {
          "kind": "Pod",
          "match": {
            "NetworkPolicy": [],
            "self": []
          },
          "model": "kubernetes"
        }
      ],
      "to": [
        {
          "kind": "Pod",
          "match": {
            "NetworkPolicy": [],
            "self": []
          },
          "model": "kubernetes"
        }
      ]
    }
  }
}

I propose displaying the following fields: kind, apiVersion, model.name, subType, and rego_query for better clarity.
This version maintains the same information but breaks it down into more structured sentences for improved readability.
Will like to hear your thoughts on this.

Hey @RipulHandoo that's great idea you've provided. I left it open because I need to deep dive on the API schema and decide the subcommands required. Anyway, we'll first look at completing components first, then we'll both work on this. What's your say? :)

Hey @RipulHandoo that's great idea you've provided. I left it open because I need to deep dive on the API schema and decide the subcommands required. Anyway, we'll first look at completing components first, then we'll both work on this. What's your say? :)

@alphaX86 Sir, the components command is ready. If possible I'll give a demo for it in today's meeting. Here is the PR for it.

@alphaX86 you still working on this issue?

@alphaX86 you still working on this issue?

Design spec not completed yet. This issue required a spec to be made

Hi @alphaX86 It's been some time since your last update. Are you still working on this issue?

@Aijeyomah Would you like to work on this issue?

@Aijeyomah Would you like to work on this issue?

Yes, I'll love to work on it

@Aijeyomah I have assigned this issue to you, remember to give regular updates to signal that you are still working on the issue and ask for community guidance in case you need it via the discussion forum.

@Aijeyomah I have assigned this issue to you, remember to give regular updates to signal that you are still working on the issue and ask for community guidance in case you need it via the discussion forum.

Alright

@Aijeyomah you still working on this ?

@Aijeyomah you still working on this ?

Yes. I will send my Pr by Monday

@Aijeyomah if you haven't started with the search command I would like to provide a hand already implemented the search myself .

@Aijeyomah if you haven't started with the search command I would like to provide a hand already implemented the search myself .

I haven't started the it. You can go ahead👍