You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature description
Due to the recent changes to how the transports work the UI needs a few updates.
Describe the feature Is your feature request related to a problem? Please describe.
Now the transport is either online or not there at all i.e. there is no offline state.
We need a UI element for setting persistent_transports
Additional context
Online/offline Transport
If there is an entry for the transport that means it is up. If there is no entry then we don't need to show anything. I.e. there is no offline state anymore.
Persistent transports
As for persistent_transports, it is just a field in the skywire visor config. On start-up, the visor takes the pk and type from it and tries to establish a connection. If the connection is successfully established the transport will showup in the usual transports field with all the required fields.
What we need is a way for the user to make changes to this persistent_transports field in the config via the UI. Because a new visor will have an empty persistent_transports in their config. And we do not want the user to make changes to the config directly. So basically the persistent_transports field is for the user to set up transports on the visor startup.
The API for persistent_transports are:
PUT /api/visors/<pk>/persistent-transports. Required json
Feature description
Due to the recent changes to how the transports work the UI needs a few updates.
Describe the feature
Is your feature request related to a problem? Please describe.
persistent_transports
Additional context
Online/offline Transport
If there is an entry for the transport that means it is up. If there is no entry then we don't need to show anything. I.e. there is no offline state anymore.
Persistent transports
As for persistent_transports, it is just a field in the skywire visor config. On start-up, the visor takes the pk and type from it and tries to establish a connection. If the connection is successfully established the transport will showup in the usual transports field with all the required fields.
What we need is a way for the user to make changes to this persistent_transports field in the config via the UI. Because a new visor will have an empty persistent_transports in their config. And we do not want the user to make changes to the config directly. So basically the persistent_transports field is for the user to set up transports on the visor startup.
The API for
persistent_transports
are:/api/visors/<pk>/persistent-transports
. Required jsonpersistent_transports
from the config will be in thesummary
.Changes can be made according to this .
The text was updated successfully, but these errors were encountered: