Improved FCM Support Supporting both Legacy and OAuth2 Methods

[caronc]

Description:

Related issue (if applicable): #326

This is an almost completely rewrite of the FCM plugin.

Now the legacy URLs work providing the Web API Token from the project page. However i've also researched how the json file works and support this too (without all of the overhead of the Google libraries). So the syntax is as follows:

Legacy Mode:

• fcm://apikey/target

OAuth2 Mode:
You can point to the JSON file generated from the Project page either by path or by web URL (if you're sharing it somewhere on your network) like so:

• fcm://project_id/target?keyfile=/path/to/keyfile
• fcm://project_id/target/target2/targetN/?keyfile=https://user:pass@localhost/web/location

Here is a better overview of what needs to be done to use the new version of this service:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• No lint errors (use flake8)
• 100% test coverage

[caronc]

@nobruramos Would you mind giving this a try as you were kind enough to help me test the FCM out before.

I've almost completely re-wrote the entire thing now to properly support the Web API Key in addition to the new OAuth2 mode. I still need to add more test coverage before I push this into the main branch though.

[nobruramos]

sure! Em qua., 3 de fev. de 2021 às 22:25, Chris Caron <notifications@github.com> escreveu:

…

@nobruramos <https://github.com/nobruramos> Would you mind giving this a try as you were kind enough to help me test the FCM out before. I've almost completely re-wrote the entire thing now to properly support the Web API Key in addition to the new OAuth2 mode. I still need to add more test coverage before I push this into the main branch though. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#353 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADVEJB5YFXCEDPZN7WD7OXDS5HZQRANCNFSM4XB4UKNQ> .