docs: clarify datastore access in role-based access control#313
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: clarify datastore access in role-based access control#313mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
Clarifies in the role-based access control docs that reading datastore connection credentials (host, port, username, password) requires the Developer or Admin role, and that Viewers cannot read these credentials.
Context
The upstream change tightens authorization on the legacy v1 datastore GET endpoints (list, get-by-name, credential), which previously returned connection credentials to any project member — including viewers. These endpoints now require at least the
developerrole, matching the existing behavior of the delete route and aligning with how datastore access is described to users.Changes
cc @noeporter for review.