aws-ssm-tunnel (new formula)

[ilkerispir]

Go-based CLI tool to port-forward into RDS & ElastiCache over SSM-managed EC2 instances.

• Source-built using Go 1.24
• Apache-2.0 licensed
• Supports interactive + quick-connect modes
• Includes session tracking (--list, --kill, --kill-all)
• Tested with AWS SSO profiles

✅ brew install --build-from-source aws-ssm-tunnel works
✅ brew test aws-ssm-tunnel passes
✅ brew audit --new-formula aws-ssm-tunnel passes

[github-actions]

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

[botantony]

1. Remove version "0.0.2"
2. bin/"aws-ssm-tunnel", "--help" is not a sufficient test, see more here: https://docs.brew.sh/Formula-Cookbook#add-a-test-to-the-formula

We want tests that don’t require any user input and test the basic functionality of the application. For example foo build-foo input.foo is a good test and (despite their widespread use) foo --version and foo --help are bad tests.

3. Homebrew doesn't accept niche packages without stars, watchers, or a lot of forks: https://docs.brew.sh/Acceptable-Formulae#niche-or-self-submitted-stuff

Consider creating your own tap: https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap

[SMillerDev]

Is the naming not correct if you leave out the output: arg?

[SMillerDev]

We need a test that exercises the some of the functionality of the app. Version checks or usage checks (foo --version or foo --help) are not sufficient, as explained in the formula cookbook.

In most cases, a good test would involve running a simple test case: run #{bin}/foo input.txt.

• Then you can check that the output is as expected (with assert_equal or assert_match on the output of shell_output)
• You can also check that an output file was created, if that is expected: assert_predicate testpath/"output.txt", :exist?

Some advice for specific cases:

• If the formula is a library, compile and run some simple code that links against it. It could be taken from upstream's documentation / source examples.
• If the formula is for a GUI program, try to find some function that runs as command-line only, like a format conversion, reading or displaying a config file, etc.
• If the software cannot function without credentials, a test could be to try to connect with invalid credentials (or without credentials) and confirm that it fails as expected.
• Same if the software requires a virtual machine, docker instance, etc. to be running.

[SMillerDev]

Hi, this seems like a nice software, but not notable enough for us to package in Homebrew for now. This is not a decision on the merits of the software, but we cannot distribute every single piece of software and have to draw a line on “notability” somewhere. Of course, we would be happy to reconsider in the future.

However, please note that "We frown on authors submitting their own work unless it is very popular."

Please consider hosting it in a personal tap, which is very easy to do: https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap