Marc Egli

Sorry I did not use this libary in the last 6 years. Consider it unsupported by now. Instead you might want to check out the fork that Matthias is maintaining:...

No that would pretty much be the only benefit. @elupus the code to handle the service account is provided by the core component in https://github.com/googleapis/google-cloud-python whats left is the different...

If we are concerned about the repetition then we should fix it by getting rid of the repetition and not by using yaml anchors. Imagine that in a world where...

@elupus the library expects a key_file and not the credentials themself, so it does not make a ton of sense to load that into the config. https://github.com/googleapis/google-cloud-python/blob/master/api_core/docs/auth.rst#service-accounts

I know it exists but I see no value in including this into the configuration. It just opens room for errors and if the key_file has a new field in...

I double checked and even at Google internally we recommend using the file instead of manually extracting the key. Those files can in theory contain more information than they now...

No the library tries to create credentials and then throws a value error if it does not succeed. The actual loading of the credentials is done by a [private function](https://github.com/googleapis/google-auth-library-python/blob/master/google/oauth2/service_account.py#L161)...

I have created an initial version https://github.com/home-assistant/home-assistant/pull/29590 next step is to allow changing of the log level and propper error handling when we can not load the file.

My use case for this is a ws2811 powered Christmas light. During normal operation I use a flicker effect to light up single pixels at a time and want them...