←back to thread

Tilt: dev environment as code

(github.com)
136 points saikatsg | 2 comments | 26 Apr 25 19:14 UTC | HN request time: 0.647s | source
Show context
patwoz ◴[26 Apr 25 21:42 UTC] No.43807456[source]▶
How does Tilt compare to “skaffold dev“? We use skaffold exactly for that purpose. To develop within a the cluster.
replies(3): >>43807561 #>>43807733 #>>43807748 #
turtlebits ◴[26 Apr 25 21:56 UTC] No.43807561[source]▶
Skaffold works but its DX is pretty poor. Too many knobs via yaml- tilt has just enough magic that it doesn't feel like a chore to setup local dev.
replies(1): >>43807644 #
cirego ◴[26 Apr 25 22:08 UTC] No.43807644[source]▶
I've always appreciated that Tilt chose Starlark instead of YAML. Makes things so much cleaner!
replies(1): >>43807708 #
1. tomjakubowski ◴[26 Apr 25 22:17 UTC] No.43807708[source]▶
Well, now you've really got me interested. Almost every case of a YAML eDSL would be better served by Starlark instead, in my Bazel-brained opinion.
replies(1): >>43807745 #
2. cirego ◴[26 Apr 25 22:23 UTC] No.43807745[source]▶
I think Tilt Extensions highlights the combined power and composability that using Starlarks brings to Tilt: https://docs.tilt.dev/extensions.html.

Want to create a Kubernetes secret? It's as simple as:

    load('ext://secret', 'secret_yaml_generic')
    k8s_yaml(secret_yaml_generic(...))
Want to create that secret from Vault instead?

    load('ext://vault_client', 'vault_read_secret', 'vault_set_env_vars')
    vault_set_env_vars('https://localhost:8200','mytoken')
    my_foo = vault_read_secret('path/myfoo', 'value')
    my_bar = vault_read_secret('path/mybar', 'foobar')