Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Tiltfile args with tilt enable #6341

Open
FFdhorkin opened this issue Mar 19, 2024 · 1 comment
Open

Support Tiltfile args with tilt enable #6341

FFdhorkin opened this issue Mar 19, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@FFdhorkin
Copy link

FFdhorkin commented Mar 19, 2024

Describe the Feature You Want

Similar to how you can define a group of services to use with tilt up and tilt down, I'd like to be able to do the same with tilt enable

Current Behavior

After configuring as per the link above, tilt enable group_name gives an error about "no such resource"

Why Do You Want This?

Suppose I have two groups, server and subset.

I can use tilt up to run everything, tilt up server to only run backend stuff, and tilt up subset to run a subset of frontend related services.

However, if I start via tilt up server and then change my mind, I have to either run tilt enable frontend_a frontend_b frontend_c or run tilt down followed by tilt up. Similarly, if I use tilt up server followed by tilt down subset, I end up in the same place.

I imagine this might be possible in a tedious fashion via local_resource duplicates of the same groups, but that seems undesirable.

Additional context
N/A

@FFdhorkin FFdhorkin added the enhancement New feature or request label Mar 19, 2024
@nicks
Copy link
Member

nicks commented Mar 26, 2024

🤔 hmmm...i think this might be the same feature request as #6137 ? i.e., provide a more ergonomic way to add and remove arguments at runtime?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants