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
Currently it is very hard to figure out what a component looks like
So I would like to propose that we add a new command to kreate in order to have the possibility to get such info
Examples
kreate get component -n <name>
where <name> is the name of the component
output
Name: name of the component
Labels: // list of labels
Annotations: // list of annotations
Status:
Links: // Links assigned to the component
Envs: // Env vars created or enriched using Link
Capabilities: // List of capabilities used: db, ...
Route: // URL of the route exposed
...
To get such info it is needed now that we execute several commands like
// To get a component or a link or a capability
kc get component/fruit-client-sb,link/link-to-fruit-backend,capability...
// To get the detail of a pod = component + env vars, ...
kc describe pod/$(kc get pod -n demo -lapp=fruit-client-sb | grep "Running" | awk '{print $1}')
// To get ENV vars created when container starts
kc exec -n demo $(kc get pod -n demo -lapp=fruit-backend-sb | grep "Running" | awk '{print $1}') env | grep DB
The text was updated successfully, but these errors were encountered:
Feature Request
Currently it is very hard to figure out what a component looks like
So I would like to propose that we add a new command to
kreate
in order to have the possibility to get such infoExamples
To get such info it is needed now that we execute several commands like
The text was updated successfully, but these errors were encountered: