Repository navigation
fix(integration-v2-warehouse): connect sources through the secure connect link - #441
Merged
Merged
Conversation
…nect link The warehouse step collected credentials in wizard_ask and passed them to the PostHog tools as tool arguments. The gateway operator prompt forbids secrets in tool arguments, so the agent reported the step as blocked. The step now sends the user to the connect page for each in-cli source. The user enters the credentials there, and the agent creates the source with the stored credential_id.
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a wizard branch:
Add Results will be posted here when complete. |
sarahxsanders
approved these changes
Oct 26, 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
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.
Problem
wizard_askand passed it todata-warehouse-source-setuporexternal-data-sources-createas a tool argument.wizard-ai-gateway-system-prompt) tells the model to keep secrets out of tool arguments, so the model refuses the step.Changes
in-clisource now goes throughdata-warehouse-source-connect-link. The user enters the credentials on the PostHog connect page, not in the terminal.connect_urlin onewizard_askper source, with two options: connected or skip.credential_idfromdata-warehouse-stored-credentials-listand callsdata-warehouse-source-setupwithpayload: { "credential_id": "<id>" }.setupwith the stored credential. Setup syncs every table in the schema the user picks on the page, and the report says so. Thedb-schema+createpath is gone, becausedatabase_schemadoes not accept acredential_id.deep-linkmode and the report and status rules do not change.context/agents/integration-v2/warehouse.mdmatches the new flow.Note
The older
data-warehouse-sourceskill (thewizard warehousecommand) still collects typed credentials. It is not changed here.How did you test this code?
pnpm testpasses. A new contract test indata-warehouse-source-skill.test.jsfails if the step skill again asks for credentials as text answers or namesexternal-data-sources-create.pnpm buildpasses.