rdme versions output isn't entirely JSON

[theholla]

Our company has some automation around the rdme versions command. I saw that as of #603, raw JSON should be the new default and the --raw is no longer available.

The issue I'm running into is that before outputting the raw JSON, the command outputs one line about auth: 🔑 someone@company.com is currently logged in, using the stored API key for this project: projectname.

I wanted to check whether this is intended, and if so if there's a way to disable the auth line? Otherwise we can update our automation to handle.

[kanadgupta]

Hi @theholla! Sorry for the trouble. The reason that auth line is printed is because the tool is detecting stored credentials in your system. Does your automation use the rdme login command? If so then I’d instead recommend passing in your API key directly into each command via the --key option. If you’re not using rdme login then it’s likely a bug on our end.

[theholla]

That did the trick, thank you! To summarize, with a previous version of the rdme package, we were using rdme login with rdme versions --raw. With the latest version, we can use rdme versions --key <KEY> to the same effect.

Thanks for your help!

[kanadgupta]

Great to hear! We definitely recommend using the --key option in automated workflows as opposed to rdme login since API keys are much safer to use than passwords. I'll make a note of this in our docs. Sorry for the disruption to your workflow!