Skip to content

wsk activation list behavior #119

@rabbah

Description

@rabbah

A recent change to the way activations are listed produced two different behaviors.

When there are no activations, the result is this:

> wsk activation list 
activations

and when repeated with activations, the result is this:

>  wsk activation list
Datetime            Activation ID                    Kind                 Start Duration   Status            Entity                                                                                              
2019-03-14 15:25:40 1d11658e3f974e6391658e3f97be63ac nodejs:6             cold  69ms       success           guest/e:0.0.1                                                                                       

@larandersson perhaps we should nuke the naked activations headers when there are no results.

additionally, can we trim the lines so that they don't overflow unnecessarily?

Screen Shot 2019-03-14 at 2 42 42 PM

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions