Address recurring customer questions in Hub docs#41
Open
alexolivier wants to merge 8 commits intocerbos:mainfrom
Open
Address recurring customer questions in Hub docs#41alexolivier wants to merge 8 commits intocerbos:mainfrom
alexolivier wants to merge 8 commits intocerbos:mainfrom
Conversation
Based on analysis of Slack customer channels (#ext-cerbos-ust, #ext-cerbos-zephyr, #ext-cerbos-bah) and prospect conversations, several questions come up repeatedly that the docs should preempt: 1. WASM vs policies confusion: Add prominent callout in ePDP docs explaining that the WASM file is the engine, not the policies, and that policy updates happen automatically without restarts. 2. ePDP vs service PDP for server-side: Add guidance that ePDP is for client-side presentational checks; server-side should use @cerbos/grpc or @cerbos/http with a service PDP. 3. Playground to production workflow: Add section explaining how to export from playground and deploy via git/policy store. 4. Audit log data storage: Add section documenting where logs are stored (cloud: GCP Netherlands, on-prem: ClickHouse) and how to integrate with SIEM/UEBA systems. 5. Multi-tenancy patterns: Add section to concepts page covering scoped policies, multiple policy stores, and the CI/CD pipeline for dynamic policy management. 6. WASM engine file size: Add note about expected engine size and caching/gitignore recommendations. Signed-off-by: Alex Olivier <alex@alexolivier.me>
- Replace "e.g." with "such as" and em dashes - Remove redundant opening statement in playground section - Use specific section anchor instead of "described above" - Reword server-side guidance for consistent tone Signed-off-by: Alex Olivier <alex@alexolivier.me>
Signed-off-by: Alex Olivier <alex@alexolivier.me>
Signed-off-by: Alex Olivier <alex@alexolivier.me>
Customers frequently ask whether Hub is required or what it adds on top of the open source PDP. Add a brief section to the index page making the distinction clear. Signed-off-by: Alex Olivier <alex@alexolivier.me>
From community.cerbos.dev/c/help analysis: - Add Cloudflare Workers WASM compatibility note to ePDP platform support section (multiple users hit instantiateStreaming issues) - Add planResources guidance for listing/filtering resources (most common performance question — users iterate checkResource instead of using the query planner) - Clarify PDP is stateless in concepts (recurring misconception that Cerbos can fetch external data) Signed-off-by: Alex Olivier <alex@alexolivier.me>
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.
Add answers to questions asked in the last few months by users