[grubmeshi]

🤖 Written by AI agent

bb-run-approve-abort

Two interactive commands let a person approve or abort a building block run without meshPanel:

• meshstack buildingblock approve-run <building-block-uuid> shows the plan of the waiting run and asks "Approve this plan? [y/N]". The approval names the predecessor run that made the shown plan, so meshStack answers 409 when the run was planned again. The CLI then asks you to review the new plan.
• meshstack buildingblock abort-run <building-block-uuid> takes the newest dry run when there is one, else the latest run, shows it and asks "Abort this run? [y/N]". A 409 means the run can no longer be aborted.

Both run only on a terminal, because the decision belongs to a person who saw the run. They follow HAL links only, from the building block to its run and from the run to its actions, and stop before asking when a link is missing. Afterwards they print the building block, because run v1 shows WAITING_FOR_APPROVAL as IN_PROGRESS and ABORTED as FAILED.

The backend, meshcloud/meshfed-release#11281, is released in v2026.43.0.

Reading order

1. feat(client): the client follows run links; the token goes only to links below the endpoint.
2. refactor: Prompt.Confirm, now used by profile delete.
3. feat: approve-run.
4. feat: abort-run.

For the Terraform provider

Nothing to do on the next bump. The new methods sit on a new Client.BuildingBlockRunAction field, so the mocks keep compiling, and the new Links field is on MeshBuildingBlockRun, which the provider does not map to a schema.

Tests

The acceptance suite here has no terminal, so it cannot drive these commands. The building-block-runner testacc cases TestAccPlanApproval, TestAccStalePlan and TestAccAbort (meshcloud/building-block-runner#86) cover approve and abort end to end. Unit tests cover what those cannot: the token stays below the endpoint, the terminal check, the approve prompt, the approved plan is the shown one, and 409 on approve.

Cross-repo PRs

• meshcloud/meshstack-cli — this PR
• meshcloud/meshfed-release#11281 — the approve and abort run endpoints and their links (released)
• meshcloud/meshfed-release#11282 — the Panel's trigger and abort follow run transparency
• feat: basic auth, client/http and the runner API in client #33 — stacks on this branch

🤖 Generated with Claude Code

[meshcloud-gh-actions]

Coverage of the acceptance run against the meshStack backend, on a20d6f4da9b15ae60ba64cc519c8abc8f7d42733.

Scope	Coverage
Unit tests	78.1%
Acceptance tests	53.7%
Combined	80.1%

Uncovered functions

client/api_key.go:55: meshApiKeyClient.Create 0.0%
client/api_key.go:59: meshApiKeyClient.Read 0.0%
client/api_key.go:63: meshApiKeyClient.Update 0.0%
client/api_key.go:71: meshApiKeyClient.Delete 0.0%
client/api_key_permissions.go:20: ApiKeyPermissions.AllCodes 0.0%
client/api_key_permissions.go:33: ApiKeyPermissions.WorkspaceCodes 0.0%
client/api_key_permissions.go:295: AllApiKeyPermissions 0.0%
client/api_key_permissions.go:299: WorkspacePermissionCodes 0.0%
client/building_block_definition.go:71: MeshBuildingBlockDefinitionApprovalPolicies.NothingRequiresApproval 0.0%
client/building_block_definition.go:82: DisabledSchedule 0.0%
client/building_block_definition.go:89: MeshBuildingBlockDefinitionSchedule.IsDisabled 0.0%
client/building_block_definition.go:93: MeshBuildingBlockDefinitionSpec.HasNeutralPolicies 0.0%
client/building_block_definition.go:97: MeshBuildingBlockDefinitionSpec.WithNeutralPolicies 0.0%
client/building_block_definition.go:166: meshBuildingBlockDefinitionClient.List 0.0%
client/building_block_definition.go:173: meshBuildingBlockDefinitionClient.Read 0.0%
client/building_block_definition.go:177: meshBuildingBlockDefinitionClient.Create 0.0%
client/building_block_definition.go:181: meshBuildingBlockDefinitionClient.Update 0.0%
client/building_block_definition.go:185: meshBuildingBlockDefinitionClient.Delete 0.0%
client/building_block_definition_version.go:100: MeshBuildingBlockType.TagInputTargets 0.0%
client/building_block_definition_version.go:245: meshBuildingBlockDefinitionVersionClient.Create 0.0%
client/building_block_definition_version.go:254: meshBuildingBlockDefinitionVersionClient.Update 0.0%
client/building_block_definition_version_implementation.go:80: MeshBuildingBlockDefinitionImplementation.InferType 0.0%
client/building_block_definition_version_implementation.go:94: MeshBuildingBlockDefinitionImplementation.MarshalJSON 0.0%
client/building_block_definition_version_implementation.go:107: *MeshBuildingBlockDefinitionImplementation.UnmarshalJSON 0.0%
client/building_block_runner.go:82: meshBuildingBlockRunnerClient.Create 0.0%
... and 126 more

covdata func names a method without its receiver, so an entry can belong to an implementation nothing selects rather than to a function the tests never reached. Open the file and line before reading one as a coverage gap.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
1.9% Duplication on New Code

See analysis details on SonarQube Cloud