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
April 24th - 2023: This proposition should be reviewed as we could also keep the credentials attached to the service identity but having the key imported within the service discovered (as it has a reference to a service identity) !
The screen (http://primaza.65.108.212.158.nip.io/services/discovered) displays the list of the discovered services (cluster/namespace) but do not allow to assign for a service discovered their credentials as currently this job is managed using the registered service (= Service identity).
I propose to do different things such as:
Add a button "credential" to each entry of the services discovered table in order to assign 1-to-Many credentials / service.
When we click on the button "credential", then we are redirected to the credential screen. This screen includes a table containing zero-to-many credentials and top of this table a form to encode a new credential
Proposition
The screen (http://primaza.65.108.212.158.nip.io/services/discovered) displays the list of the discovered services (cluster/namespace) but do not allow to assign for a service discovered their credentials as currently this job is managed using the registered service (= Service identity).
I propose to do different things such as:
servicesDiscovered
using the entityServicesDiscovered
Related to tickets: #299 #300
The text was updated successfully, but these errors were encountered: