GoogleContainerTools/skaffold

Skaffold file output flags are inconsistent

Open

#3,150 opened on Nov 1, 2019

View on GitHub
 (3 comments) (1 reaction) (1 assignee)Go (1,416 forks)batch import
area/cliarea/uxfixithelp wantedjuly-chillkind/feature-requestpriority/p2

Repository metrics

Stars
 (12,822 stars)
PR merge metrics
 (Avg merge 3d 6h) (16 merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Examine the flag definitions in the Skaffold codebase for 'build', 'deploy', and 'render' commands, then propose a unified naming convention for file output flags.
Tech stack
go
Domain
backendclidevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoSkaffold
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65