Nick Santos

:thinking: hmmm...i think this might be the same feature request as https://github.com/tilt-dev/tilt/issues/6137 ? i.e., provide a more ergonomic way to add and remove arguments at runtime?

thanks! i'm pretty certain there's _some_ bug here where tilt isn't doing the path normalization correctly, but not sure what it is yet... :thinking:

@lizzthabet and i spent some time looking into this, and whew, case-sensitivity filepath canonicalization in Go is not great. there's some C and Rust code that we might need to...

i believe the way it currently works is that `tilt` generates a custom kubeconfig for subprocesses to use with only one context, sets the KUBECONFIG environment variable, and helm respects...

There doesn't appear to be any bug report here, so I'm going to close this issue. Let me know if I missed something!

Sure, can you add more details on what you tried, what you expected to happen, and what happened instead?

for what it's worth, here are the repro steps i tried: 1. Created two kubectl contexts -- kind, and a dummy kubectl context connected to a dead cluster. 2. `kubectl...

we received a bug report about kube contexts not resolving correctly sometimes if you were using docker compose and kubernetes in the same tiltfile - https://github.com/tilt-dev/tilt/issues/6453 was that possibly the...

sure, here's what i tried: https://github.com/tilt-dev/tilt-extensions/pull/624 seems to work correctly: https://app.circleci.com/pipelines/github/tilt-dev/tilt-extensions/1726/workflows/0f14996e-bca2-4753-8fb4-dbd6b96b1b4a/jobs/4203

@blast-hardcheese hmm...i think you're confused. the only repro case in this issue is https://github.com/tilt-dev/tilt-extensions/pull/624 , which demonstrated that tilt is currently working as expected. if you have a repro case,...