Set flag pro by reading both --tcp and --pro

[zechen0]

The pro flag is used to enable pro-specific options such as opening all ports. The --pro command line arg is deprecated in favor of --tcp. We keep both for now but will remove --pro in the future.

Signed-off-by: Ze Chen zechenbit@gmail.com

Description

Will fix #89

How Has This Been Tested?

Provision VM to run inlets-server in Azure

create --provider=azure --subscription-id=ffffffffffffffffffff --region=eastus --access-token-file=client_credentials.json --pro

Output

[82/500] Host: inlets-pedantic-dijkstra9|deployment-f7af6665-3949-4b87-bcf9-343960eaecd2, status: Running
[83/500] Host: inlets-pedantic-dijkstra9|deployment-f7af6665-3949-4b87-bcf9-343960eaecd2, status: active
inlets PRO (0.8.1) exit-server summary:
  IP: 40.114.94.81
  Auth-token: XNYxykHfVpo1ToMFwgtmjCt0wUe9slhKFcvZGxibmMX0iwQ9r007z0TgvM1ePLJC

Command:

# Obtain a license at https://inlets.dev
export LICENSE="$HOME/.inlets/license"

# Give a single value or comma-separated
export PORTS="8000"

# Where to route traffic from the inlets serverx
export UPSTREAM="localhost"

inlets-pro client --url "wss://40.114.94.81:8123/connect" \
  --token "XNYxykHfVpo1ToMFwgtmjCt0wUe9slhKFcvZGxibmMX0iwQ9r007z0TgvM1ePLJC" \
  --license-file "$LICENSE" \
  --upstream $UPSTREAM \
  --ports $PORTS

To delete:
  inletsctl delete --provider azure --id "inlets-pedantic-dijkstra9|deployment-f7af6665-3949-4b87-bcf9-343960eaecd2"

Client was able to connect server.

➜  inlets inlets-pro client --url "wss://40.114.94.81:8123/connect" \
  --token "XNYxykHfVpo1ToMFwgtmjCt0wUe9slhKFcvZGxibmMX0iwQ9r007z0TgvM1ePLJC" \
  --license-file "$LICENSE" \
  --upstream $UPSTREAM \
  --ports $PORTS

2021/02/17 23:54:11 Starting TCP client. Version 0.8.0-dirty - 7d2137f283e67490d64ea68903f7d49b9c9463c3
2021/02/17 23:54:11 Licensed to: Ze Chen ******
2021/02/17 23:54:11 Upstream server: 192.168.101.100, for ports: ****
inlets-pro client. Copyright Alex Ellis, OpenFaaS Ltd 2020
INFO[2021/02/17 23:54:12] Connecting to proxy                           url="wss://40.114.94.81:8123/connect"

How are existing users impacted? What migration steps/scripts do we need?

No impact.

Checklist:

I have:

• [x] updated the documentation and/or roadmap (if required)
• [x] read the CONTRIBUTION guide
• [x] signed-off my commits with git commit -s
• [ ] added unit tests