routing: control-planes routing should be the single root of our application

[johncowen]

Description

At the root our our application routing we currently have three siblings:

• / itself (i.e. Home/ControlPlanesDetailView)
• /meshes (the Mesh listing MeshListView)
• /zones (the Zone listing ZoneListView)

This is incorrect as a mesh and a zone live inside a control plane.

We should have a single root / (i.e. "control plane root" which we don't currently have) with two children as siblings

• / (i.e. "control plane root" which we don't currently have)
  • overview itself (i.e. Home/ControlPlanesDetailView)
  • meshes (the Mesh listing MeshListView)
  • zones (the Zone listing ZoneListView)

This then gives us a place to apply/display things always for an entire single control plane instead of using App.vue to do so.

---

Perhaps separately (or perhaps not) to this, I would really like to get to the point where we 'mount' our routing configurations ontop of each over from the outside rather than from the inside (we currently do this from the inside meaning tight-coupling of dependencies):

i.e.

// kinda pseudo-code

controlPlaneRoutes

// mount(theRoutes, 'where.to.mount.them')

mount(meshRoutes, 'control-planes')
mount(serviceRoutes, 'control-planes.meshes')
mount(dataplaneRoutes, 'control-planes.meshes')
mount(subscriptionRoutes, 'control-planes.meshes.dataplanes')
mount(networkingRoutes, 'control-planes.meshes.dataplanes')

mount(zoneRoutes, 'control-planes')
mount(subscriptionRoutes, 'control-planes.zones')

mount(ingressRoutes, 'control-planes.zones')
mount(subscriptionRoutes, 'control-planes.zones.ingresses')
mount(networkingRoutes, 'control-planes.zones.ingresses')

mount(egressRoutes, 'control-planes.zones')
mount(subscriptionRoutes, 'control-planes.zones.egresses')
mount(networkingRoutes, 'control-planes.zones.egresses')

This way we have full modular control of our routes (and reusable routes) from The Outside (i.e. looser coupling of dependencies)