Hey Jacob,
Thanks for the prompt and detailed reply! It's encouraging to know that I'm not crazy after all ;-) I'm also more than willing to give you guys the benefit of the doubt being that this just became a possibility like two days prior to me attempting to use it!
Great to hear that it's on the radar, I'll be eagerly keeping my eye out. For what it's worth, I ran into what I can only assume is
very similar issue (if not identical) with the
google-cloud-node library, specifically with crypto operations as I'm attempting to sign files living in GCS for short-lived access. That one operation seems to have the same exact issue in the interim, whereas the rest of the operations I'm performing (eg. pulling from PubSub subscriptions) work fine.
In the short term, I'm blocked on that as well for my specific use case, but I appreciate that you've given me an idea for a workaround as far as Firebase Admin is concerned if it ends up getting resolved first! For now, I'm using my existing credentials.
Best,
Dan
P.S. -- FWIW as far as my specific use case goes, I'm interested in the Application Default Credentials to avoid having to ship around credentials securely. It's something that I'd ideally not commit to SCM or a Docker image. Of course I could use something like Kubernetes secrets, but it's just one more moving piece!