dbt Wizard CLI setup: Snowflake API key entry fails silently

Help
1

Hello, this is my first post. Please forgive if I didn’t tag this properly. I’m trying to submit a possible “bug report” for dbt Wizard CLI setup.

The problem I’m having

During intial setup with dbt Wizard CLI, I try to configure Snowflake provider. When it prompts for Snowflake API key and I paste it, dbt Wizard closes and returns me to Powershell prompt with no additional feedback, a “silent failure” of sorts.

The context of why I’m trying to do this

dbt Wizard CLI setup, configuring Snowflake provider

What I’ve already tried

GitHub Copilot provided a manual workaround to configure the provider and key. This worked and Snowflake provider is now configured.
Recommended workaround (reliable path)

  1. Skip the initial setup screen for now.
  2. Configure Snowflake directly with provider commands:
    1. Enter key:
      $key = Read-Host “Paste Snowflake API key”
      $key | wizard providers set-key snowflake
    2. Set Snowflake account id:
      wizard providers snowflake set-account-id YOUR_ACCOUNT_ID
    3. Enable provider:
      wizard providers enable snowflake
    4. Verify:
      wizard providers list

If I perform these steps and then get back into wizard, initial setup continues with success and I’m able to query Snowflake data.

Other info

  1. Product: dbt Wizard
  2. Version: 0.1.1-beta.61
  3. OS + terminal: Windows + VS Code integrated PowerShell
  4. Symptom: entering Snowflake API key in setup screen immediately returns to shell with no error text
  5. Expected: key should be accepted and setup should continue
  6. Repro steps:
  7. Launch wizard
  8. Enter setup flow
  9. Choose Snowflake
  10. Paste API key and press Enter
  11. Observe immediate return to prompt, no feedback
  12. Workaround that succeeds:
  13. wizard login
  14. wizard providers set-key snowflake
  15. wizard providers snowflake set-account-id stuller-prod
  16. wizard providers enable snowflake
  17. Snowflake queries then work
  18. Impact:
  19. blocks first-run onboarding
  20. appears as silent failure, difficult to self-diagnose