GoogleContainerTools/skaffold

Additional helm flags per release

Open

#2,959 opened on Sep 28, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (12,822 stars) (1,416 forks)batch import
area/deploydeploy/helmhelp wantedkind/feature-requestpriority/p3

Description

Currently additional helm flags can only be specified that apply to all releases, it would be ideal to be able to specify per-release helm flags this would provide better flexibility for workarounds such as issue #1665 where --repo could be added as an install flag

Contributor guide

Tech stack
go
Domain
devopscli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingSkaffold helm deployer internalsHelm concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Examine how additional helm flags are currently applied globally in the skaffold deploy code (likely in pkg/skaffold/deploy/helm/). Understand the schema for helm releases and how to extend it to allow per release flags. Reference the existing workaround in issue #1665 for context on the ' repo' flag use case.
Additional helm flags per release · GoogleContainerTools/skaffold#2959 | Good First Issue