Python SDK for CloudEvents
Go to file
Yurii Serhiichuk 21572afb57
Fix Pydantic custom attributes (#229)
* Add custom extension attribute to the test set.

Replicates bug test data from the https://github.com/cloudevents/sdk-python/issues/228

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>

* use modern `super` syntax

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>

* Fix `black` language version

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>

* Fixes https://github.com/cloudevents/sdk-python/issues/228

Pydantic v2 .__dict__ has different behavior from what Pydantic v1 had and is not giving us `extra` fields anymore. On the other hand the iterator over the event gives us extras as well

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>

* Add missing EOF

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>

* Add Pydantic fix to the changelog

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>

* Add links to the changelog

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>

* Bump version

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>

* Update Black and MyPy versions

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>

---------

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>
2023-10-30 06:44:36 +01:00
.github Add Python 3.11 support (#209) 2023-01-04 11:33:33 -07:00
cloudevents Fix Pydantic custom attributes (#229) 2023-10-30 06:44:36 +01:00
requirements Pydantic v2 native implementation (#219) 2023-09-20 22:59:13 +03:00
samples release: v1.6.0 (#189) 2022-08-18 07:24:20 -07:00
.clomonitor.yml rename (#160) 2022-04-27 12:48:44 -04:00
.coveragerc refactor: create abstract cloudevent (#186) 2022-08-06 14:52:22 +03:00
.gitignore Make SDK compliant with CloudEvents SDK spec 2018-12-08 09:10:20 -05:00
.pre-commit-config.yaml Fix Pydantic custom attributes (#229) 2023-10-30 06:44:36 +01:00
CHANGELOG.md Fix Pydantic custom attributes (#229) 2023-10-30 06:44:36 +01:00
CONTRIBUTING.md Add some CLO stuff (#158) 2022-04-26 14:38:38 -04:00
LICENSE Initial commit 2018-09-21 18:42:34 -04:00
MAINTAINERS.md Governance docs per CE PR 1226 (#221) 2023-09-21 22:59:54 +03:00
MANIFEST.in Introduce typings (#207) 2023-01-04 08:29:41 -07:00
README.md add link to our security mailing list (#226) 2023-10-16 19:14:38 +03:00
RELEASING.md ci: migrate to `main` branch (#180) 2022-07-15 11:22:29 +03:00
mypy.ini Introduce typings (#207) 2023-01-04 08:29:41 -07:00
pypi_packaging.py ci: migrate to `main` branch (#180) 2022-07-15 11:22:29 +03:00
pyproject.toml Feat/dev env cleanup (#167) 2022-07-10 12:53:37 +03:00
setup.py Adds a pydantic V2 compatibility layer (#218) 2023-08-28 20:09:53 +03:00
tox.ini Add Python 3.11 support (#209) 2023-01-04 11:33:33 -07:00

README.md

Python SDK for CloudEvents

PyPI version

Status

This SDK is still considered a work in progress, therefore things might (and will) break with every update.

This SDK current supports the following versions of CloudEvents:

  • v1.0
  • v0.3

Python SDK

Package cloudevents provides primitives to work with CloudEvents specification: https://github.com/cloudevents/spec.

Installing

The CloudEvents SDK can be installed with pip:

pip install cloudevents

Sending CloudEvents

Below we will provide samples on how to send cloudevents using the popular requests library.

Binary HTTP CloudEvent

from cloudevents.http import CloudEvent
from cloudevents.conversion import to_binary
import requests

# Create a CloudEvent
# - The CloudEvent "id" is generated if omitted. "specversion" defaults to "1.0".
attributes = {
    "type": "com.example.sampletype1",
    "source": "https://example.com/event-producer",
}
data = {"message": "Hello World!"}
event = CloudEvent(attributes, data)

# Creates the HTTP request representation of the CloudEvent in binary content mode
headers, body = to_binary(event)

# POST
requests.post("<some-url>", data=body, headers=headers)

Structured HTTP CloudEvent

from cloudevents.conversion import to_structured
from cloudevents.http import CloudEvent
import requests

# Create a CloudEvent
# - The CloudEvent "id" is generated if omitted. "specversion" defaults to "1.0".
attributes = {
    "type": "com.example.sampletype2",
    "source": "https://example.com/event-producer",
}
data = {"message": "Hello World!"}
event = CloudEvent(attributes, data)

# Creates the HTTP request representation of the CloudEvent in structured content mode
headers, body = to_structured(event)

# POST
requests.post("<some-url>", data=body, headers=headers)

You can find a complete example of turning a CloudEvent into a HTTP request in the samples' directory.

Receiving CloudEvents

The code below shows how to consume a cloudevent using the popular python web framework flask:

from flask import Flask, request

from cloudevents.http import from_http

app = Flask(__name__)


# create an endpoint at http://localhost:/3000/
@app.route("/", methods=["POST"])
def home():
    # create a CloudEvent
    event = from_http(request.headers, request.get_data())

    # you can access cloudevent fields as seen below
    print(
        f"Found {event['id']} from {event['source']} with type "
        f"{event['type']} and specversion {event['specversion']}"
    )

    return "", 204


if __name__ == "__main__":
    app.run(port=3000)

You can find a complete example of turning a CloudEvent into a HTTP request in the samples' directory.

SDK versioning

The goal of this package is to provide support for all released versions of CloudEvents, ideally while maintaining the same API. It will use semantic versioning with following rules:

  • MAJOR version increments when backwards incompatible changes is introduced.
  • MINOR version increments when backwards compatible feature is introduced INCLUDING support for new CloudEvents version.
  • PATCH version increments when a backwards compatible bug fix is introduced.

Community

Each SDK may have its own unique processes, tooling and guidelines, common governance related material can be found in the CloudEvents docs directory. In particular, in there you will find information concerning how SDK projects are managed, guidelines for how PR reviews and approval, and our Code of Conduct information.

If there is a security concern with one of the CloudEvents specifications, or with one of the project's SDKs, please send an email to cncf-cloudevents-security@lists.cncf.io.

Additional SDK Resources

Maintenance

We use black and isort for autoformatting. We set up a tox environment to reformat the codebase.

e.g.

pip install tox
tox -e reformat

For information on releasing version bumps see RELEASING.md