#17934 support some sort of interpolation or dynamic generation of helm deployment namespace Issue created by cburroughs Is your feature request related to a problem? Please describe. We have some shared environments like

qa

or

stage

where we generally would expect fixed namespaces to exist in k8s. However, in

dev

we have both "shared" environments (team A deploys service foo from CI and team B expects to be able to integrate against it) and "playground" style namespaces like

devname-tmp-trying-out-deploying-with-pants

. I'd like some way of deploying a cool new service to a "playground/personal" namespace, show it to another engineer who can do the same without conflict, while still having defined in pants the Official Namespace for CI/production. Describe the solution you'd like Some sort of string interpolation or other environmental variable injection to

helm_deployment.namespace

Describe alternatives you've considered • passing

-- --namespace=mynamesapce

which results in

InvalidHelmPassthroughArgs

• Settings kube contexts as described in https://www.pantsbuild.org/docs/helm-deployments#deploying This works great for a single chart, but has fricting when working on multiple applications since you need to either keep track of the current active context as you twiddle the namespaces, or (outside of pants in bash or whatnot) manage target:namespace mappings. Additional context New to both helm and the pants integration, but it is very spiffy! pantsbuild/pants