Skip to content

[v18] MWI: Add tbot start noop to start or configure bots with no services#63666

Merged
timothyb89 merged 2 commits intobranch/v18from
bot/backport-63624-branch/v18
Feb 11, 2026
Merged

[v18] MWI: Add tbot start noop to start or configure bots with no services#63666
timothyb89 merged 2 commits intobranch/v18from
bot/backport-63624-branch/v18

Conversation

@timothyb89
Copy link
Contributor

@timothyb89 timothyb89 commented Feb 9, 2026

Backport #63624 to branch/v18

changelog: MWI: Add new tbot start no-op helper that starts no services

Manual testing

  • Built and ran tbot start noop --join-uri=... --storage=./storage

This adds a new `noop` start/configure mode to tbot that starts no
services.

While of dubious utility on its own, the intent is to add a CLI flow
that mirrors our [documentation flow], where we first onboard a bot,
then configure services in a follow-up guide. Currently,
`tbot configure` can only generate a configuration with a service, so
it isn't able to help generate the initial empty YAML config file.

Additionally, it is useful for verifying onboarding config and making
sure the bot can join the cluster.

[documentation flow]: https://goteleport.com/docs/machine-workload-identity/deployment/linux/
@timothyb89 timothyb89 added this pull request to the merge queue Feb 11, 2026
Merged via the queue into branch/v18 with commit 9cd0bf5 Feb 11, 2026
42 checks passed
@timothyb89 timothyb89 deleted the bot/backport-63624-branch/v18 branch February 11, 2026 05:14
@doggydogworld doggydogworld mentioned this pull request Feb 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments