The k-toolbar should have a k-accordion with a k-button to list EVCs. Something like (with text as List EVCs):
Once the button is clicked it should make a request to GET this.$kytos_server_api + "kytos/mef_eline/v2/evc/. For more information about mef_eline API check out this OpenAPI rendered spec. telemetry_int uses mef_eline EVCs metadata to enable/disable INT, so you can rely on mef_eline EVCs metadata.
Side note related to adjacent work: actions to enable/disable/redeploy in bulk will be implemented on a new k-info-panel, that k-info-panel will receive as props all mef_eline EVCs, so this k-button is expected to emit an event to display the new k-info-panel. The shape of the metadata and which keys and values you should expect to understand whether INT is enabled or not will be specified in the issue where the k-info-panel will be implemented.
Example getting http://127.0.0.1:8181/api/kytos/mef_eline/v2/evc/ (with 1 existing EVC with INT enabled too):
Once the button is clicked it should make a request to
GET this.$kytos_server_api + "kytos/mef_eline/v2/evc/
. For more information about mef_eline API check out this OpenAPI rendered spec.telemetry_int
usesmef_eline
EVCs metadata to enable/disable INT, so you can rely on mef_eline EVCs metadata.Side note related to adjacent work: actions to enable/disable/redeploy in bulk will be implemented on a new k-info-panel, that k-info-panel will receive as props all mef_eline EVCs, so this k-button is expected to emit an event to display the new k-info-panel. The shape of the metadata and which keys and values you should expect to understand whether INT is enabled or not will be specified in the issue where the k-info-panel will be implemented.
Example getting
http://127.0.0.1:8181/api/kytos/mef_eline/v2/evc/
(with 1 existing EVC with INT enabled too):