`k8s_yaml` set resource name
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Describe the Feature You Want
While working with a ton of different resources in a Tiltfile I stumbled upon the need to set clear resource dependencies. Surprisingly this is much easier with non-drect k8s resources such as local_resource. Being able to set an explicit resource name for all resources that will be created in a single k8s_yaml call only seems natural.
I'd imagine this feature to overwrite the default behavior of automatic resource naming, and group all resources created within a single call to the resource name explicitly set as a parameter.
Current Behavior
In my workflow I first (want to) deploy a set of CRDs defined in a kustomize file, after which I deploy a bunch of helm charts with helm_resource. To currently set up a dependency tree, I have to manually dig through resource names with tilt get uiresource, only to find out they're not clearly named, so I'd have to explicitly name them with k8s_resouce, for each CRD one by one.
Why Do You Want This?
This quickly grows to become a massive overhead when you start deploying more and more resources in a Tiltfile.
Additional context
It seems like such a natural thing to explicitly name k8s resources as we can do with other resources that I wouldn't be surprised if there has been thought about this before, so am I overlooking something here that makes this hard to implement?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the k8s_yaml resource-naming path and comparing it with k8s_resource naming behavior. The feature should accept an explicit resource name for resources created by one k8s_yaml call, group them under that name, and support clear dependency configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- developer-experience, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100