Fixes https://emqx.atlassian.net/browse/EMQX-9603 Rather than relying on a JWT worker to produce and refresh tokens, we could just produce then on demand when pushing the messages to GCP PubSub. That can generate a bit of extra work (as multiple processes might realize it’s time to refresh the JWT and do so), but that shouldn’t be much. In return, we avoid any possibility of not having a fresh JWT when pushing messages. |
||
|---|---|---|
| .. | ||
| src | ||
| test | ||
| BSL.txt | ||
| README.md | ||
| rebar.config | ||
EMQX GCP Pub/Sub Bridge
Google Cloud Pub/Sub is a messaging service provided by Google Cloud Platform (GCP).
The application is used to connect EMQX and GCP Pub/Sub. User can create a rule and easily ingest IoT data into GCP Pub/Sub by leveraging EMQX Rules.
Documentation
-
Refer to Ingest Data into GCP Pub/Sub for how to use EMQX dashboard to ingest IoT data into GCP Pub/Sub.
-
Refer to EMQX Rules for the EMQX rules engine introduction.
HTTP APIs
-
Several APIs are provided for bridge management, which includes create bridge, update bridge, get bridge, stop or restart bridge and list bridges etc.
Refer to API Docs - Bridges for more detailed information.
Contributing
Please see our contributing.md.
License
EMQ Business Source License 1.1, refer to LICENSE.