Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 4.0.0.Alpha8
    • Component/s: CLI
    • Labels:
      None

      Description

      When you launch the CLI you can pass a --bind=xxx param which then controls the client side bind address used for connections. But you can't specify this with the connect command itself.

      This is minor; I just noticed it while experimenting with the fix for WFCORE-2225 when I wanted to confirm the fix was working by using the CLI.

      Also, I noticed that if I did a "connect --bind=192.168.1.10" the CLI accepted the invalide command.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  iweiss Ingo Weiss
                  Reporter:
                  brian.stansberry Brian Stansberry
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: