GoogleContainerTools/skaffold

Skaffold file output flags are inconsistent

Open

#3,150 建立於 2019年11月1日

在 GitHub 查看
 (3 留言) (1 反應) (1 負責人)Go (12,822 star) (1,416 fork)batch import
area/cliarea/uxfixithelp wantedjuly-chillkind/feature-requestpriority/p2

描述

Skaffold supports writing a few different run results to files for use in other commands or k8s-related processes. However, these files all have different flag names, making it difficult to know which one to use for which command.

writing the built artifact results from skaffold build - --file-output consuming this generated file in skaffold deploy - --artifacts, or -a outputting templated manifests from skaffold render - --output, or -o

We should decide on a common flag name and just use that everywhere, or at least for build and render where the flag is actually specifying an output.

貢獻者指南

技術棧
go
領域
clideveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
GoSkaffold CLIflag handling
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Review the current flag definitions for 'skaffold build', 'skaffold deploy', and 'skaffold render' in the cmd/skaffold/app/cmd directory. The issue highlights file output, artifacts, and output flags. Propose a unified flag name and implement changes across the affected commands. Also update any related documentation.