feat: trigger a building block run from the CLI - #11
Closed
JohannesRudolph wants to merge 1 commit into
Closed
JohannesRudolph wants to merge 1 commit into
JohannesRudolph wants to merge 1 commit into
Conversation
|
Coverage of the acceptance run against the meshStack backend, on
Uncovered functions
|
JohannesRudolph
commented
Sep 22, 2026
| } | ||
|
|
||
| func (c meshBuildingBlockV2Client) TriggerRun(ctx context.Context, bbUuid string) (err error) { | ||
| // MeshBuildingBlockV2TriggerRunRequest is the body of a trigger-run. DryRun asks for a DETECT run, |
Member
Author
There was a problem hiding this comment.
remove useless comment, these are already covered by API docs authoritatively and should not be restated in the clinet code
JohannesRudolph
force-pushed
the
feat/cli-bb-run-logs
branch
from
October 1, 2026 10:18
20a9c6b to
64da43c
Compare
Add `meshstack buildingblock trigger-run <uuid> [--dry-run]`. It asks meshStack to run a building block and writes the building block that meshStack answers with. --dry-run asks for a DETECT run. This lets agents and scripts start a run without a local OpenTofu, for example after a fix is pushed to a draft definition's branch. The command does not wait for the run and does not approve anything. Approval stays with humans in meshPanel. The client gets TriggerRunWith, which takes the dryRun flag and returns the answered building block. TriggerRun keeps its signature and calls it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JohannesRudolph
force-pushed
the
feat/buildingblock-trigger-run
branch
from
October 1, 2026 10:19
8fb6cca to
2819ea5
Compare
JohannesRudolph
marked this pull request as ready for review
October 1, 2026 10:20
This was referenced Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
meshstack buildingblock trigger-run <uuid> [--dry-run] [-o json|ndjson].Why: agents and scripts can ask meshStack for a run without a local OpenTofu, e.g. after pushing a fix to a draft definition's branch. The command does not wait and approves nothing. Approval stays with a human in meshPanel.
It writes the building block meshStack answers with (202). The run starts asynchronously, so
status.latestRunUuidmay still name the previous run.The call sits on its own
client.Client.RunTrigger, so the provider'sMeshBuildingBlockV2Clientmock is unaffected.Stacked on #10.
🤖 Generated with Claude Code