GoogleContainerTools/skaffold

Should Event API follow CNCF's Cloud Events

Open

#4,259 建立於 2020年5月26日

在 GitHub 查看
 (5 留言) (0 反應) (1 負責人)Go (12,822 star) (1,416 fork)batch import
area/eventinggood first issuehelp wantedidekind/feature-requestpriority/p2

描述

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?

貢獻者指南

技術棧
go
領域
backendapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
understanding of CloudEvents specificationfamiliarity with skaffold's event APIGo programming knowledge
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
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.