v0.8.0

Fixes:

• Little potential nil pointer dereferences in several connect commands

Changes:

• Ability to establish a tunnel to an arbitrary address and port through an direct TCP connection: Now, there is a command bbb connect direct {TARGET_ID} to establish a TCP connection

Notes:
Usage of the command: bbb connect direct {ttcp_xxxxx}

Contributors:
@achetronic

v0.7.0

Changes:

• Ability to establish a tunnel to an arbitrary address and port through an SSH connection: Now, there is a flag in bbb connect ssh --local-port-forwarding {SOME DATA NEEDED HERE} to establish a connection using your ssh as a bastien

Notes:
Usage of the command: bbb connect ssh {ttcp_xxxxx} -l 4646:{remote host here}:4646

Contributors:
@jaimeph

v0.6.0

Changes:

• Ability to establish connections through redis CLI: There is a new subcommand connect redis. The new command open a connection against a target and open the redis CLI pointing to it.

Notes:
Usage of the command: bbb connect redis {ttcp_xxxxx}

Contributors:
@dfradehubs

v0.5.0

Changes:

• There is a new command upgrade: executing it will upgrade your bbb to the latest version.
  Are you willing to contribute supporting --version flag to avoid pointing always to latest?

• BOUNDARY_ADDR environment variable is not always required: now it's only verified for those commands that actually use it, such as: auth, list, connect

Notes:
Usage of the command: bbb upgrade

Contributors:
@achetronic

v0.4.0

Changes:

• Flag --insecure deleted from command connect browser: From now, the command will try http protocol and will switch to https on failure automatically

• Command version now is crafted automatically: Previously, before each release, we set the version manually according to the reference just to be released. This process is now automated.

Notes:
Usage of the command: bbb connect browser {ttcp_xxxxx}

Contributors:
@achetronic

v0.3.0

Changes:

• Command connect browser doesn't force having credentials. This way, some internal web GUIs can be accessed. If some credentials are brokered, then the previous behavior remains

• Released binaries are created statically from now: some people reported problems because bbb was looking for some missing C shared libraries

Notes:
Usage of the command: bbb connect browser {ttcp_xxxxx}

Contributors:
@dfradehubs @achetronic

v0.2.1

Fixes:

• Improve UX on connect browser . Now it's fancy as others
  • successful connection messages are now as fancy as others
  • Ctrl+Z is captured to allow graceful exit

Notes:
Usage of the command: bbb connect browser {ttcp_xxxxx}

Contributors:
@achetronic

v0.2.0

Features:

• Ability to establish connections through browsers:

  • Now there is a new subcommand connect browser. The new command open a connection against a target and open the browser pointing to it.

  • It's able to work with basic and bearer authentication depending on the target configuration on H.Boundary:

    • Basic authentication requires username and password configured on the target
    • Bearer authentication requires ONLY password configured on the target

  • There is a new flag --insecure (defaulted to false) to force http scheme instead of https in the URL

Notes:
Usage of the new command: bbb connect browser {ttcp_xxxxx}

Contributors:
@achetronic @dfradehubs

v0.1.0

Highligths:

• Give fancy suggestions when Boundary CLI is not installed
• Ability to perform OIDC authentication
• Ability to list organizations, their projects and give automated abbreviations for the last ones
• Ability to list targets owned by projects
• Ability to establish SSH connections
• Ability to establish Kubernetes connections during hours
• Fancy messages to enjoy your usage
• Target type detection: It prevents user from connecting using SSH helper when a target is configured for Kubernetes and viceversa
• Detection for needed CLIs: boundary, ssh, kubectl: no more odd failures

Contributors:
@achetronic @sebastocorp