-
Notifications
You must be signed in to change notification settings - Fork 242
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
Problems running freshly built pd utility #39
Comments
@cmluciano can you share the CLI usage you are trying? |
I have tried
But all just return the help menu. |
@cmluciano can you test with the master, if it persist? |
I can get the version to print no problem, but I still has an exit code of 1.
|
OK I figured it out. This was a mixture of stale dependencies local with the cli library. A "super fresh" build fixed everything. |
😎 thanks again for reporting the issue. let me know if you hit any other bugs. this library is under development, likely to have bugs /missing features till we hit a stable milestone. I'll cut a release (binary will be available on the github release page), as and when we reach there. |
I am trying to run the utility but i can't get anything to output aside from the help menu. When running the utility and inspecting the return code, I am getting a 1. This makes me think that I might be hitting this line https://github.com/PagerDuty/go-pagerduty/blob/master/command/main.go#L123 but I don't get any other errors even if I swap stderr with stdout.
My initial impression is that it keeps hitting this help menu because something was wrong with my api key that I tried to pass with -authtoken="MYKEY" and with the alternative ~/.pd.yml. I tested out the escalation policy example was able to get results with the key, so it should be a valid key.
I'll keep digging into the code, but I thought it would be worth creating an issue to track this as well.
The text was updated successfully, but these errors were encountered: