feat: [DBOPS-2504]: dbops resource targets new /v1/llm-authoring/execute-pipeline contract#309
Draft
vivonk wants to merge 3 commits into
Draft
feat: [DBOPS-2504]: dbops resource targets new /v1/llm-authoring/execute-pipeline contract#309vivonk wants to merge 3 commits into
vivonk wants to merge 3 commits into
Conversation
…ute-pipeline contract Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> AI-Session-Id: db29f72a-8854-4dae-add7-5eb45b95868f AI-Tool: claude-code AI-Model: unknown
The db-devops-service execute endpoint now resolves the K8s connector server-side from the DBOPS instance (PR #1422 commit 0cd71a8f). The skill should not need to know about K8s connectors or how to resolve one from instance.connector — it's a server-side detail. Removed from src/registry/toolsets/dbops.ts: - Resource bodySchema field 'k8s_connector_ref' - bodyBuilder forwarding of k8s_connector_ref / k8sConnectorRef - Mentions in description / actionDescription Tests updated to match. Required body fields are now schema_id, instance_id, conversation_id, changeset (plus mutually-exclusive pipeline_identifier or use_default_pipeline).
…ction Move database_execute_llm_authoring_pipeline from operations.create to executeActions.run with risk=low_write. The action triggers an existing pipeline (not creating a YAML resource), and the user has already consented via the changeset review card — a medium_write elicitation prompt was redundant and stacked multiple approval cards on the Harness chat client. - operations.create -> executeActions.run - risk: medium_write -> low_write (below requiresConfirmation threshold) - Preserve bodyBuilder / bodySchema / responseExtractor verbatim - Resource description now points the model at harness_execute action=run - Update unit tests in tests/registry/dbops.test.ts (dispatchExecute / "run") and tests/registry/toolsets/dbops.test.ts (executeActions.run lookup) to match the new resource shape Co-Authored-By: Claude <noreply@anthropic.com> AI-Session-Id: db29f72a-8854-4dae-add7-5eb45b95868f AI-Tool: claude-code AI-Model: unknown
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
1 participant
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.
Description
Updates the
+ "database_execute_llm_authoring_pipeline" +dbops resource to call the new server-side orchestrator endpoint shipped in db-devops-service, which atomically triggers an LLM-authoring validate-and-preview pipeline and persists the billable+ "ChangeAuthoringExecutionEvent" +for flex billing.What changed in
src/registry/toolsets/dbops.ts:/dbops/v1/orgs/{org}/projects/{project}/execute-llm-authoring-pipeline→/v1/orgs/{org}/projects/{project}/llm-authoring/execute-pipeline(matches the new db-devops-service endpoint).bodyBuilderrewritten: acceptsinput.body ?? input(dual-shape) and either snake_case or camelCase keys; always emits the five required fieldsconversationId, schemaId, instanceId, changeset, k8sConnectorRef; exactly-one branch enforced (useDefaultPipeline=trueORpipelineIdentifier+ optionalruntimeInputs).bodySchemadocuments all eight input fields forharness_describe.actionDescriptionupdated to call out the NG setting (dbops_llm_authoring_pipeline), mutual exclusivity, and the four reserved input keys.Tests:
tests/registry/toolsets/dbops.test.ts— 5 vitest unit cases covering: path; custom-pipeline branch; default-pipeline branch; double-wrap (input.body); already-camelCase passthrough.tests/registry/dbops.test.ts— 1 stale dispatch test replaced with 2 tests that exercise both branches via the registry. Without this update the full suite would stay red because the old test asserted the old contract.pnpm test→ 1864/1864 passed,pnpm typecheckclean,pnpm buildclean.Cross-repo PRs needed for end-to-end:
dbops_changesetskill to call this resource (NG-setting branch + AskUserQuestion + drop in-skill polling).Type of Change
Checklist
pnpm test→ 1864 passed)pnpm typecheckclean)