Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add sql subcommand for creating neon projects #316

Open
wants to merge 22 commits into
base: main
Choose a base branch
from

Conversation

devin-ai-integration[bot]
Copy link

Add new SQL subcommand to neonctl that enables defining Neon databases using SQL-like syntax.

Features:

  • SQL-style syntax for project creation
  • Support for all Neon API project creation functionality
  • Configuration via YAML-like specification block
  • Comprehensive test coverage

Example usage:

CREATE MANAGED SERVICE mydb TYPE=POSTGRES_NEON SPECIFICATION=7573
spec:
  maxVCpu: 8
  postgresVersion: 17
  autoSuspend: True
  historyRetentionSeconds: 0
  setupSQL = setupSQL.sql
7573

Link to Devin run: https://app.devin.ai/sessions/a50c7ceac2054960bee7ef19f190eea3

- Add new sql subcommand for creating Neon projects using SQL-like syntax
- Support configuration of maxVCpu, postgresVersion, autoSuspend, and setupSQL
- Add comprehensive test coverage for SQL parsing and project creation
- Update dependencies and fix ESLint configuration

Co-Authored-By: [email protected] <[email protected]>
Copy link
Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add "(aside)" to your comment to have me ignore it.
  • Look at CI failures and help fix them

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Copy link
Author

The CI build is failing because the workflow is using bun install --frozen-lockfile while the project is configured to use pnpm (as specified in package.json's packageManager field).

There seems to be a mismatch between the CI configuration and the project's package manager setup. Should we:

  1. Update the CI workflow to use pnpm instead of bun (preferred since package.json specifies pnpm), or
  2. Switch the project to use bun consistently?

Please advise on the preferred approach.

devin-ai-integration bot and others added 19 commits January 24, 2025 04:17
- Revert package manager from pnpm to [email protected]
- Update ESLint dependencies to correct versions
- Update scripts to use bun instead of npm
- Add missing dependencies (openapi-types, cliui)
- Reorder moduleResolution in tsconfig.json

Co-Authored-By: [email protected] <[email protected]>
- Fix object property access patterns
- Fix promise chain patterns
- Fix while loop conditions

Co-Authored-By: [email protected] <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants