feat: make resource name required on all provisioning tools#7
Merged
Conversation
The InstaNode API now requires the `name` field on every provisioning endpoint. The six create_* resource tools (postgres, cache, nosql, queue, storage, webhook) already required `name`; this makes `create_deploy`'s `name` required too — it was the only optional one. - create_deploy: `name` schema is no longer .optional(); description clarifies it is required. - client.ts: CreateDeployParams.name is now required; createDeploy always appends `name` to the multipart form. - Bump 0.9.0 -> 0.10.0 (package.json, server.json, User-Agent). - README: note `name` required on create_deploy. - Sync stale package-lock.json (was @instant/mcp@0.4.0). Build (tsc) and test.sh both pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Reconcile mandatory resource naming with master's create_deploy private/allowed_ips params. create_deploy now requires `name` AND supports private deploys + IP allowlists. Version bumped to 0.11.0 (next minor over master's 0.10.1). package-lock.json regenerated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
namefield strictly required on all provisioning endpoints. This updates the MCP server to match.create_*resource tools (create_postgres,create_cache,create_nosql,create_queue,create_storage,create_webhook) already requirednamevia the sharednameArgZod schema — no change needed there.create_deploywas the only provisioning tool with an optionalname. Its Zod schema is now required (no.optional()), the tool description statesnameis required, and the client always appendsnameto the multipart form.create_stack/stack-creation tool exists in this MCP server, so nothing to change there.client.ts:CreateDeployParams.nameis now a requiredstring.0.9.0->0.10.0(package.json,server.json,User-Agentheader).create_deployrow and Container deployment section notenameis required.package-lock.json(was@instant/mcp@0.4.0).Test plan
npm install+npm run build(tsc) — cleannpm test(test.sh) — all 8 tests pass, includingcreate_postgres rejects empty nameand thecreate_deploysmoke test (passesname)create_deploywith nonameis now rejected by Zod schema validation🤖 Generated with Claude Code