Skip to content

Conversation

@aezell
Copy link
Contributor

@aezell aezell commented Jan 23, 2026

Summary

  • Fixes issue where fly launch with web customization always showed fly-db in the DATABASE_URL secret, even when the user specified a custom database name
  • When attaching to an existing Managed Postgres cluster, the DATABASE_URL now correctly uses the database name provided in the web form
  • Checks for both "db_name" and "name" keys in form data to handle API/UI naming conventions

Test plan

  • Run fly launch and customize via web UI
  • Select an existing MPG cluster and provide a custom database name
  • Verify the DATABASE_URL secret shows the custom database name instead of fly-db

🤖 Generated with Claude Code

…cluster

When attaching to an existing Managed Postgres cluster during launch,
the DATABASE_URL secret now correctly uses the database name provided
by the user in the web customization form, instead of always defaulting
to "fly-db".

Changes:
- webui.go: Check for both "db_name" and "name" keys in form data
- launch_databases.go: Parse and modify connection URI to use custom
  database name when attaching to existing cluster

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@aezell aezell merged commit 4caca5f into master Jan 26, 2026
24 checks passed
@aezell aezell deleted the alex/fix_customized_db_name branch January 26, 2026 14:57
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.

2 participants