-
-
Notifications
You must be signed in to change notification settings - Fork 12.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloud-sql-proxy v2.6.1 (new formula) #140782
Conversation
Formula/c/cloud-sql-proxy.rb
Outdated
|
||
test do | ||
assert_match "cloud-sql-proxy version #{version}", shell_output("#{bin}/cloud-sql-proxy --version") | ||
assert_match "could not find default credentials", shell_output("echo $(#{bin}/cloud-sql-proxy test 2>&1)") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
assert_match "could not find default credentials", shell_output("echo $(#{bin}/cloud-sql-proxy test 2>&1)") | |
assert_match "could not find default credentials", shell_output("#{bin}/cloud-sql-proxy test 2>&1") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The echo
here is used to suppress the exit 1 return status code (see other example in kamel.rb).
I found a better way to handle it using the second argument of shell_output
though, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yeah, Kamel shouldn't do that either.
cloud-sql-proxy v2.6.1 (add test case) cloud-sql-proxy v2.6.1 (fix test case) cloud-sql-proxy v2.6.1 (add livecheck) cloud-sql-proxy: use default livecheck Signed-off-by: Rui Chen <rui@chenrui.dev>
d5069af
to
ba546f9
Compare
@jhandguy thanks for your first PR to homebrew-core! 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @jhandguy!
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?