GoogleContainerTools/skaffold

Should Event API follow CNCF's Cloud Events

Open

#4,259 opened on May 26, 2020

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Go (12,822 stars) (1,416 forks)batch import
area/eventinggood first issuehelp wantedidekind/feature-requestpriority/p2

Description

We should consider standardizing our Event API to follow CNCF's https://cloudevents.io/ standard.

Benefits: better alignment with the space, standardized format which aligns better with best practices Cons: IDEs will need to restructure their clients

Thoughts?

Contributor guide

Tech stack
go
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
understanding of CloudEvents specificationfamiliarity with skaffold's event APIGo programming knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Review the existing Event API implementation in the skaffold codebase (likely in the 'event' package). Analyze the CloudEvents specification and how it could be adopted. Consider the impact on existing clients and discuss trade offs in the issue comments. Look at the assignee's comments for direction on the scope of changes.