-
Notifications
You must be signed in to change notification settings - Fork 15
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
autoendpoint: modify FCMCredentials to accept String #254
Comments
Maybe? Kind of the point you're making here. There might be a way to do it using file handoffs, but it's going to be messy because I don't always know if I have write access. I can try writing to |
The See the |
This is a good point and likely a good way around the tmp file solution. |
FCM credentials are now specified as a JSON structure with an embedded credential string. Please note that additional escaping may be required. the original `auth_file` parameter is now deprecated. As per above, please specify the FCM credential file content as an included String. Additional string escapes may be required to properly specify the inline JSON. Closes #254
Can we modify FCM credentials to accept a string instead of PathBuf? It looks like the yup_oauth2 library only supports a Path in
read_service_account_key
, but perhaps we could create a temp file out of the auth file string and pass that to the library?The text was updated successfully, but these errors were encountered: