Skip to content

docs: Document the Insights database access flag - #764

Open
FXschwartz wants to merge 1 commit into
mainfrom
insights-database-access
Open

docs: Document the Insights database access flag#764
FXschwartz wants to merge 1 commit into
mainfrom
insights-database-access

Conversation

@FXschwartz

Copy link
Copy Markdown
Contributor

Serverpod 4.0 disabled the Insights database access endpoints by default (serverpod/serverpod#5606). Add the enableDatabaseAccess option to the Insights page, the 4.0 upgrade guide, and the configuration reference, and note the removed hotReload, getOpenSessionLog, and shutdown methods.

Comment on lines +93 to +95
### If you use Insights database access

The Insights endpoints that give database access (`fetchDatabaseBulkData`, `runQueries`, `getDatabaseRowCount`, and `executeSql`) are disabled by default in 4.0 and throw an `AccessDeniedException` until enabled. If you rely on them, for example to browse tables from the Insights app, opt in per environment with `enableDatabaseAccess` in the `insightsServer` block of the config file (or the `SERVERPOD_INSIGHTS_SERVER_ENABLE_DATABASE_ACCESS` environment variable):

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: This section is not completely accurate. The Insights app doesn't use the database endpoints, which must be very clear for users (on every place that we mention the database access flag). It only exists to support custom operations that use the service client.

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