Auth doesn't work with HEROKU_API_KEY env variable without netrc

[exalted]

heroku used to work in the older version with HEROKU_API_KEY variable set only, but current version will complain if it can't find netrc file.

I understand that heroku (toolbelt) is thought for end users mainly, but we're using it as a part of our system (as a dependency) to run commands on heroku on users' behalf, and I don't see a way to do that anymore.

Any plans to "fix" this please?

/cc: @as-cii

[jdx]

definitely a bug, shouldn't be too hard to fix either. I hope to get to this this week, in the meantime you should be able to stub out the netrc file with any info so long as you have the env var

[exalted]

Thanks.

[jdx]

first of all, apologies this took me a bit to get to, the ruby 1.8.7 removal took a bit out of my time last week. Regardless, I finally got to looking at this and realized you're probably talking about the current v3 version of the cli (this repo is for the yet-to-be-fully-released v4 version of the cli).

This ended up being a pretty simple fix, it's here: heroku/legacy-cli#1502

[exalted]

👏

[as-cii]

first of all, apologies this took me a bit to get to, the ruby 1.8.7 removal took a bit out of my time last week

Thanks a lot for taking the time to evaluate and answer our question: you're doing an amazing job with this new version of the toolbelt and we're looking forward to seeing it released ✨

This ended up being a pretty simple fix, it's here: heroku/legacy-cli#1502

As far as I understand the proposed fix does not address the problem we were experiencing when we first opened this issue. Our feature request, if you will, was to be able to use the HEROKU_API_KEY env variable as our preferred authentication method while using the CLT. In particular, we'd like to use it with the heroku-fork plugin which, as far as I know, works with the new version of the toolbelt.

So, to rephrase the original question: is there any plan to support HEROKU_API_KEY as an authentication mechanism for e.g. plugins? This is what we ended up doing to support it for the time being (https://github.com/catchup/da-fork/commit/048b6221e2ffd4bdb22b310ad8a67bf7a5a32c53#diff-201b94283d87538569750fac4c036c0eR64)

Thanks again 🙇

[jdx]

fix is in! 6badae8

(not released just yet though)

[as-cii]

@dickeyxxx ❤️💛💚💙

Awesome job! Thank you! ✨