fix(influxdb3): Ent 3.10 user management API reference descriptions#7369
Merged
Conversation
Implements 2 suggestions from #7362 review: - All "user with permission to X" descriptions (8 occurrences). Permissions come from roles, not users — reword to "a user whose **roles** have permission. - `GET /api/v3/users_by_oauth_id/{oauth_id}`. Real consumer is our CLI — consider **not exposing** to customers unless there's a feature ask. @abshierjoel reviewed the 3.10 Enterprise API spec on [docs-v2#7362](#7362) (merged). Six comments on the **user-management / RBAC** endpoint descriptions — two literal suggestions applied before merge, four outstanding. Co-authored-by: Joel Abshier <31899323+abshierjoel@users.noreply.github.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.
What changed
Implements 2 suggestions from #7362 review:
All "user with permission to X" descriptions (8 occurrences). Permissions come from roles, not users — reword to "a user whose roles have permission.
GET /api/v3/users_by_oauth_id/{oauth_id}. Real consumer is our CLI — consider not exposing to customers unless there's a feature ask.Why
@abshierjoel reviewed the 3.10 Enterprise API spec on docs-v2#7362 (merged). Six comments on the user-management / RBAC endpoint descriptions — two literal suggestions applied before merge, four outstanding.
Related
These descriptions are revised from comments in the source repo so we'll also need to fix them there.