docs(forest-runtime): schema CREATE privilege + version-pinned npm info - #20
Merged
Merged
Conversation
… in npm info Review feedback: creating the dedicated schema needs database-level CREATE, so document the pre-created-schema fallback (the executor probes pg_namespace before creating, so schema-level privileges suffice then). Also query peerDependencies for the installed agent version — bare 'npm info' answers for latest, whose executor pin may differ. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
Addresses two review comments left on #18 (they targeted
forest-runtime.mdx, which the #18 rebase moved out of that PR — the text now lives onmainvia #19).forestschema requires theCREATEprivilege on the database; a role with table rights in an existing schema can't create one, soagent.start()would fail. Documented the fallback: an administrator pre-creates the schema and grants access — the executor probespg_namespacebefore creating (seeschema-migrations.ts), so schema-level privileges are then enough.npm infoversion — barenpm info @forestadmin/agent peerDependenciesanswers forlatest, whose executor pin may differ from the agent you run; nownpm info @forestadmin/agent@<your-agent-version> peerDependencies.🤖 Generated with Claude Code
Note
Document CREATE privilege requirement and version-pinned npm query for forest-runtime
@forestadmin/agent@<your-agent-version> peerDependencies, clarifying that npm defaults tolatestif no version is specified.CREATEprivilege to create the dedicatedforestPostgres schema, that existence is checked before creation, and that schema-level privileges suffice if the schema is pre-created.Macroscope summarized e0906fb.