Conversation
The setup wizard's createNewServiceOfType() was sending empty parameters {},
causing PostgreSQL and MongoDB service creation to fail with validation errors
('database' is required, 'username' is required).
Now fetches the parameter schema from the API to discover required fields,
auto-generates sensible defaults (database/username derived from service name),
and includes retry logic if creation fails.
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.
Summary
createNewServiceOfType()in the setup wizard sending emptyparameters: {}, which caused PostgreSQL and MongoDB service creation to fail with'database' is requiredvalidation errorsdatabaseandusernamederived from the sanitized service name)Details
Root cause: The wizard's
createNewServiceOfType()always sentparameters: {}. The backend (PostgresParameterStrategy::validate_for_creation) requiresdatabaseandusernamefor PostgreSQL (and MongoDB). Redis and S3 don't require any parameters.Fix approach:
GET /external-services/types/{service_type}/parametersto get the JSON Schemarequiredarray from the schemadatabaseandusernameare derived from the service name (e.g.,postgres-mlqhtf4m→postgres_mlqhtf4m)auto_generate_missing()Files changed:
apps/temps-cli/src/lib/service-setup.ts