This project has been archived by its maintainers, and is no longer receiving any updates.
GCES - Google Cloud Event System
Goals
This project aims make it easier to have a global Event Publisher/Event Subscriber system to be used accross services.
Architecture
Quick Event Notification Example
from gces import EventPublisher
ept = EventPublisher('gces')
ept.notify('SIGNUP_EVENT', {'user_id': 1234})
ept.notify('LOGIN_EVENT', {'user_id': 4321})
Quick Event Subscription Example
import time
from gces import (
EventSubscriber
)
def example_run_subscriber_function(data):
print("Data Received: {}".format(data))
TOPIC_NAME = 'gces'
SUBSCRIBER_NAME = 'gces_example'
es = EventSubscriber(TOPIC_NAME, SUBSCRIBER_NAME)
es.register_fsub('EXAMPLE_RUN_FUNCTION_PROCCESS' example_run_subscriber_function)
es.start()
if __name__ == '__main__':
try:
while True:
time.sleep(200)
except KeyboardInterrupt:
print('Bye!!!!')
Google Cloud Credentials
- Create Credentials at Google
- export GOOGLE_APPLICATION_CREDENTIALS=$(pwd)/<credentials_file>.json
Metadata
Release files for gces 0.0.13a0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gces-0.0.13a0.tar.gz | 5.6 kB | Without provenance | Details |
Release files / gces-0.0.13a0.tar.gz
| Download URL | gces-0.0.13a0.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3422e6150b23cbc75eb23be9e19b94e672c9a9773def386dbb2d528793e6b80
|
|
BLAKE2b-256 checksum How to use checksums |
5d5b7f034a311cbf92e5e1ec017f09d216381a4f9c80dd1ab7306c6c1747fbaa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.49.0 CPython/3.6.7
|
Security for gces 0.0.13a0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.