Description
Is your feature request related to a problem? Please describe.
Yes. While Boundary CLI currently allows easy connection to PostgreSQL databases using the boundary connect postgres command, there is no similar connect helper available for MySQL. This leads to:
- Organizations using MySQL being unable to fully leverage Boundary,
- Users having to manually connect using -exec mysql commands,
- An inconsistent user experience between PostgreSQL and MySQL,
- Security vulnerabilities such as passwords being exposed on the command line.
Describe the solution you'd like
I would like the CLI to support a new built-in helper command:
`boundary connect mysql`
This would make connecting to MySQL targets as seamless as boundary connect postgres, using the same UX patterns.
Describe alternatives you've considered
- Users manually opening a tunnel and executing commands using boundary connect -exec mysql,
- Fetching session information with boundary connect -format json and generating the mysql command via custom wrapper scripts,
- Establishing connections through session plugins or SSH-based solutions.
However, these methods are error-prone, not user-friendly, and degrade the experience provided by the CLI.
Explain any additional use-cases
- Developers being able to connect to MySQL with a single command, using Vault or static credentials,
- Users needing quick access in training and demo scenarios,
- Operations teams logging in directly to perform system checks,
- Providing a consistent user experience (command-level consistency) for both PostgreSQL and MySQL connections,
- Secure, audit-trail-supported MySQL access via the CLI.
Additional context
I plan to submit a PR that adds support for this functionality. The implementation would follow the same architecture and UX as the existing connect postgres helper, including support for credential resolution, local tunneling, and CLI integration.
This would also enable further expansion of boundary connect helpers in the future (e.g., redis, mssql).
Would love to hear your feedback before submitting the PR.