Skip to content

Any chances of exposing Shell session details to VertxCommand extensions ? #15

Description

@ramukima

For example, say I have two commands A.a and B.b. When A.a is run it initializes a map entry in vert.x shared data. When B.b is run, it fetches that data and uses it to perform the operation. Now, in order to make the shared-data not accessible to 'all sessions' to the shell, but within a given session... the session id for the shell may be required. Other alternative could be to build such capability outside the core of this module, which may seem like a hack.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions