Buttons. Icons. APIs.
Recently I showed you how to add a custom button to a resource and cloyingly teased there was more to come.
Well, dear reader, more has come! The latest version of Tilt not only comes with a shiny new resource overview layout but also adds support for navbar buttons. Navbar buttons appear in the fixed header, so you can always access them regardless of which resource you have selected.
Adding navbar buttons to your
Tiltfile is very similar to adding resource-specific buttons: the
uibutton extension can take care of it with a couple argument tweaks.
The hardest part of adding a navbar button is picking the icon!
Tilt includes the Material Icons set or you can provide your own SVG (ideal for brand icons or honking).
As the Tilt champion at your company, you might be used to helping debug configuration issues with your coworkers. Let’s build a button to gather some useful information about their Tilt setup and pre-compose a report to save ourselves some time!
We’ll use a Python script that runs
tilt doctor and
tilt get session to pre-populate an email:
We add a new button to invoke the script by using the
uibutton extension in our
load('ext://uibutton', 'cmd_button', 'location')
# create a button to run the linter for the 'frontend' resource
argv=['python3', 'tilt-feedback.py', sys.executable],
sys.executablecontains the path to the Tilt binary, which our Python script uses to invoke Tilt to gather diagnostics
This is pretty similar to creating a resource-specific button, but instead of specifying a
resource, we passed
Additionally, since navbar buttons in Tilt are icons with text-on-hover, we provided an icon name from the Material Icons font.
tilt up and check it out!
You’re now ready to go on your way to bedazzle your Tilt, but if you’re curious about the APIs used by this extension under the hood, read on…
More and more parts of Tilt are being exposed as APIs to allow building upon and extending built-in Tilt functionality. You might have seen our post a while back introducing the Tilt apiserver.
One of the newer types is
UIButton - we can view the
tilt-feedback button we created above using the Tilt CLI:
tilt get -o=yaml uibuttons tilt-feedback
If you’ve edited Kubernetes YAML files, this hopefully looks familiar!
spec is our configuration including the icon and placement while the
status is the current state, which in the case of a button just includes the last time that it was clicked.
What is not part of the
UIButton resource is anything related to the Python command, but we know a command runs when we click the button because I included a GIF above and everything on the internet is true, right?
For the skeptics, one of the core Tilt types in the apiserver is
Cmd, which handles execution commands on the local machine running Tilt.
The extension created a
Cmd resource along with the
UIButton resource, so let’s take a look at it:
tilt get -o=yaml cmd btn-tilt-feedback
Here, the extension populated
spec with the
argv we specified as well as
Tilt uses the
startOn field to watch other resources and invoke the command when any of those resources change appropriately. In this case, whenever the
tilt-feedback has its
lastClickedAt field in the status updated, the command will execute.
There’s a lot of power here: Tilt’s
local_resource uses a similar pattern with the
restartOn field and
FileWatch objects, for example.
As Tilt’s API grows, there will be more and more possibilities to connect these foundational types in new and inventive ways!
If you’re using the Tilt API, be sure to let us know!