Skip to content

Document which engines support updating database users - #1247

Merged
anup-deka merged 2 commits into
digitalocean:mainfrom
shabtaisharon:clarify-update-user-supported-engines
Oct 1, 2026
Merged

anup-deka merged 2 commits into
digitalocean:mainfrom
shabtaisharon:clarify-update-user-supported-engines

Conversation

@shabtaisharon

@shabtaisharon shabtaisharon commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Follow-up to Clarify that MongoDB user roles cannot be updated via the API #1239 after docs review: Update User returns 422 for MySQL (and other unsupported engines), not only MongoDB.
  • Endpoint description now lists only the supported engines (PostgreSQL, Kafka, OpenSearch), notes that other engines return 422, and keeps the MongoDB recreate guidance for role changes (per Kate's recommendation).
  • Align user_settings_update schema description with the same supported-engines + 422 wording.
image

Call out that Update User is supported for PostgreSQL, Kafka, and
OpenSearch, and that other engines (including MySQL) return 422, while
keeping the MongoDB recreate guidance for role changes.
Document the unprocessable entity response returned when the operation
is not supported for the cluster type (e.g. MySQL or MongoDB).
@shabtaisharon
shabtaisharon force-pushed the clarify-update-user-supported-engines branch from f6d6a78 to f0994b0 Compare October 1, 2026 17:43
@anup-deka
anup-deka merged commit 0267e38 into digitalocean:main Oct 1, 2026
7 checks passed
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