Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1.4
-
Fix Version/s: 2.2.0
-
Component/s: Command 'topology-list'
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Description |
Nowadays, Petals CLI has no command reporting state of a container.
A right place to get this information is the information returned by the command '{{topology-list}}', where the container state could be displayed as following: {code} petals-cli@host:port> topology-list Domain: Domain 1 * Subdomain: SubDomain 1 ** Container: Node1 (STARTED) *** information ** Container: Node2 (STOPPED) *** information ** Container: Node2 (UNKNOWN) *** information * Subdomain: SubDomain 2 ... {code} Possible container states are: {{Started}}, {{Stopped}}, {{Unknown}} |
Nowadays, Petals CLI has no command reporting state of a container.
A right place to get this information is the information returned by the command '{{topology-list}}', where the container state could be displayed as following: {code} petals-cli@host:port> topology-list Domain: Domain 1 * Subdomain: SubDomain 1 ** Container: Node1 (Started) *** information ** Container: Node2 (Stopped) *** information ** Container: Node2 (Unknown) *** information * Subdomain: SubDomain 2 ... {code} Possible container states are: {{Started}}, {{Stopped}}, {{Unknown}} |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 2.2.0 [ 10404 ] | |
| Resolution | Fixed [ 1 ] |
| Link |
This issue depends on |