Honeybadger CLI errors when the deploy command is called with any option

[griffordson]

When running the honeybadger CLI for the deploy command like so:

bundle exec honeybadger deploy --repository=abc ...

The CLI always returns an error like:

invalid option: --repository=abc

Whichever option you pass in first errors in this same way. It doesn't matter if you call it using the --repository=abc, --repository abc, or -r abc format for the options.

[subzero10]

Hey @griffordson, thank you for submitting an issue!

I just tried the command and I can't reproduce your issue:

bundle exec honeybadger deploy -e staging -r repo-does-not-exist -s 0.0.1 -u pan
Deploy notification complete.

Also:

bundle exec honeybadger deploy --environment=staging --repository=repo-does-not-exist --revision=0.0.2 --user=pan
Deploy notification complete.

I'm wondering if there are some characters in value of the repository that cause the parsing to fail. Can you try wrapping with quotes (")? Something like this:

bundle exec honeybadger deploy --environment=staging --repository="[email protected]:honeybadger-io/honeybadger-ruby.git" --revision=0.0.2 --user=pan

Finally, what version of the gem do you have installed? Can you try with the latest version?

[halfbyte]

Hi @griffordson I took another look at this and your output looks really peculiar.

Am I right in assuming that the actual deploy registration does work? (There's the "deploy notification complete." message that suggests a successful API call).

The one thing this looks like is if you maybe somewhere in an unusual place have required "test/unit" - honeybadger, for rails applications loads the environment to enable you to configure honeybadger via Rails configuration files. I can generate the exact same output as you have when I require "test/unit" in config/application.rb in a fresh Rails app.

[stympy]

Closing due to lack of activity