Go SDK for CloudEvents
Official CloudEvents SDK to integrate your application with CloudEvents.
This library will help you to:
- Represent CloudEvents in memory
- Use Event Formats to serialize/deserialize CloudEvents
- Use Protocol Bindings to send/receive CloudEvents
Note: Supported CloudEvents specification: 0.3, 1.0
Note: Supported go version: 1.14+
Add the module as dependency using go mod:
% go get github.com/cloudevents/sdk-go/v2@v2.3.1
And import the module in your code
import cloudevents "github.com/cloudevents/sdk-go/v2"
To send a CloudEvent using HTTP:
func main() {
// The default client is HTTP.
c, err := cloudevents.NewDefaultClient()
if err != nil {
log.Fatalf("failed to create client, %v", err)
}
// Create an Event.
event := cloudevents.NewEvent()
event.SetSource("example/uri")
event.SetType("example.type")
event.SetData(cloudevents.ApplicationJSON, map[string]string{"hello": "world"})
// Set a target.
ctx := cloudevents.ContextWithTarget(context.Background(), "http://localhost:8080/")
// Send that Event.
if result := c.Send(ctx, event); cloudevents.IsUndelivered(result) {
log.Fatalf("failed to send, %v", result)
}
}
To start receiving CloudEvents using HTTP:
func receive(event cloudevents.Event) {
// do something with event.
fmt.Printf("%s", event)
}
func main() {
// The default client is HTTP.
c, err := cloudevents.NewDefaultClient()
if err != nil {
log.Fatalf("failed to create client, %v", err)
}
log.Fatal(c.StartReceiver(context.Background(), receive));
}
To marshal a CloudEvent into JSON:
event := cloudevents.NewEvent()
event.SetID("example-uuid-32943bac6fea")
event.SetSource("example/uri")
event.SetType("example.type")
event.SetData(cloudevents.ApplicationJSON, map[string]string{"hello": "world"})
bytes, err := json.Marshal(event)
To unmarshal JSON back into a CloudEvent:
event := cloudevents.NewEvent()
err := json.Unmarshal(bytes, &event)
- Look at the complete documentation: https://cloudevents.github.io/sdk-go/
- Dig into the godoc: https://godoc.org/github.com/cloudevents/sdk-go/v2
- Check out the samples directory for an extended list of examples showing the different SDK features
- There are bi-weekly calls immediately following the Serverless/CloudEvents call at 9am PT (US Pacific). Which means they will typically start at 10am PT, but if the other call ends early then the SDK call will start early as well. See the CloudEvents meeting minutes to determine which week will have the call.
- Slack: #cloudeventssdk channel under CNCF's Slack workspace.
- Email: https://lists.cncf.io/g/cncf-cloudevents-sdk
- Contact for additional information: Scott Nichols (
@Scott Nichols
on slack).
Each SDK may have its own unique processes, tooling and guidelines, common
governance related material can be found in the
CloudEvents community
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.