🤖 Auto-Update: API Documentation OpenAPI Spec by SohamRatnaparkhi · Pull Request #343 · hydra-db/mintlify-docs

SohamRatnaparkhi · 2026-10-28T19:19:03Z

Auto-generated from hydradb-application @ 63732238aa1599bce293d1032ca8a9384146677d (main).
Merging deploys docs via Mintlify. Review api-reference/v2/openapi.json before merging.

^{Need help on this PR? Tag @codesmith-bot with what you need.}

…a1599bce293d1032ca8a9384146677d Signed-off-by: hydradb-bot <hydradb-bot@users.noreply.github.com>

mintlify · 2026-10-28T19:19:05Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
cortex-ai	🟢 Ready	View Preview	Oct 28, 2026, 7:19 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

github-actions · 2026-10-28T19:19:22Z

✅ Mintlify Hygiene

No issues found.

openhack-agent · 2026-10-28T19:19:35Z

✅ OpenHack Summary

Security review of 🤖 Auto-Update: API Documentation OpenAPI Spec. 1 changed file; 0 findings at or above the low reporting threshold.

0 0 0 0

Confidence Score: 5/5

No reportable security findings were detected in this scan.

Security merge-readiness rubric: 1 = critical, 2 = high, 3 = medium, 4 = low, 5 = no reportable findings. This score reflects scan findings, not a guarantee of correctness or complete coverage.

Files Needing Attention: None

Important Files Changed

api-reference/v2/openapi.json (modified)

Last reviewed commit: 8766c69 · View review on OpenHack

TIP: Mention @openhack-agent in a PR comment to request a review or ask a question. Use @openhack-agent fix all for every finding, or @openhack-agent fix unresolved threads for open review threads only.

openhack-agent

OpenHack reviewed this commit. See the OpenHack Summary for the confidence score and fix actions.

… to autogen - Access Control: a Google Drive-only section on files shared with a group: what google_group_membership_resolves reports, why a false result keeps group-shared files restricted, and the fix (reconnect as a Workspace admin with Directory access). States that no other connector reports it. - Connectors: removing a member, or a member leaving, revokes every key they created in the workspace, and re-inviting restores none. A provider whose acl_supported HydraDB withdraws stops enforcing and keeps enforce_acl. - Update Connector: the 503 when the provider catalog cannot be read while enabling enforce_acl. - api-reference/v2/openapi.json goes back to main. The generated spec (#343) now carries acl_supported, acl_description and enforce_acl from the API's own annotations, so this PR no longer hand-edits it and the two do not conflict. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Soham Ratnaparkhi <soham@hydradb.com>

greptile-apps · 2026-10-28T19:21:54Z

Confidence Score: 4/5

[Low impact] The PR reaches API reference readers, not server execution.

The PR appears safe to merge, with two non-blocking documentation fixes recommended.

Findings

Unrelated responses show ACL warnings ▶
ACL request instructions disappear ▶

Summary

This update documents connector ACL enforcement, response warnings, connector health details, and Google Group lookup support.

Connector docs explain how ACL enforcement changes setup and query results.
Connector status replies explain what failed and whose problem it is.

_{Reviews (1) · Last reviewed commit: "chore(docs): update OpenAPI spec from hy..." · Reviewed by Greptile}

greptile-apps · 2026-10-28T19:21:57Z

+              "warnings": [
+                {
+                  "code": "acl_ignored_by_connector_enforcement",
+                  "message": "This connector enforces ACL, so the request's acl was ignored."
+                }
+              ]


Unrelated responses show ACL warnings

The new examples show acl_ignored_by_connector_enforcement on feedback submissions, ingestion, deletion, and other operations that do not read with a request acl. The warnings description limits this notice to enforced reads. These examples make readers expect an ACL override where it does not apply. Keep the warning example on enforced reads and omit it from unrelated responses.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

greptile-apps · 2026-10-28T19:21:57Z

        "properties": {
          "acl": {
-            "description": "Principals to query as: emails or `user_email:`, `group:` or `domain:` principals. Returns their context plus public and unrestricted context. Omit, `[]` or `[\"*\"]` for no scoping.",
+            "description": "Optional principals for non-enforced connectors. Enforced connectors use the caller and return `acl_ignored_by_connector_enforcement` only when `acl` is supplied.",


ACL request instructions disappear

The replacement acl descriptions explain enforced connectors but remove the accepted principal forms and the no-scoping behavior for non-enforced connectors. The relations parameter also loses its repeated-or-comma-separated instructions. Users now need a separate guide to build these requests. Preserve those details alongside the new enforcement caveat.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

* docs(connectors): document source permission enforcement (PRO-3222 PRO-3223) Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com> * fix(docs): validate permission examples (PRO-3222 PRO-3223) Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com> * fix(docs): clarify ACL behavior outside enforced connectors (PRO-3223) Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com> * docs(connectors): standardize ACL enforcement terms (PRO-3222 PRO-3223) Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com> * docs: simplify connector ACL contract Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com> * docs: correct provider ACL field names Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com> * docs(connectors): let writers set ACL enforcement (PRO-3222) Signed-off-by: SohamRatnaparkhi <92905626+SohamRatnaparkhi@users.noreply.github.com> Co-authored-by: Soham Ratnaparkhi <soham@hydradb.com> * docs(acl): Drive group membership, key revocation, and leave the spec to autogen - Access Control: a Google Drive-only section on files shared with a group: what google_group_membership_resolves reports, why a false result keeps group-shared files restricted, and the fix (reconnect as a Workspace admin with Directory access). States that no other connector reports it. - Connectors: removing a member, or a member leaving, revokes every key they created in the workspace, and re-inviting restores none. A provider whose acl_supported HydraDB withdraws stops enforcing and keeps enforce_acl. - Update Connector: the 503 when the provider catalog cannot be read while enabling enforce_acl. - api-reference/v2/openapi.json goes back to main. The generated spec (#343) now carries acl_supported, acl_description and enforce_acl from the API's own annotations, so this PR no longer hand-edits it and the two do not conflict. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Soham Ratnaparkhi <soham@hydradb.com> --------- Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com> Signed-off-by: SohamRatnaparkhi <92905626+SohamRatnaparkhi@users.noreply.github.com> Signed-off-by: Soham Ratnaparkhi <soham@hydradb.com> Co-authored-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com> Co-authored-by: SohamRatnaparkhi <92905626+SohamRatnaparkhi@users.noreply.github.com> Co-authored-by: Soham Ratnaparkhi <soham@hydradb.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

chore(docs): update OpenAPI spec from hydradb-application @ 63732238a…

8766c69

…a1599bce293d1032ca8a9384146677d Signed-off-by: hydradb-bot <hydradb-bot@users.noreply.github.com>

SohamRatnaparkhi added automated docs labels Oct 28, 2026

mintlify Bot deployed to staging October 28, 2026 19:19

View deployment

openhack-agent Bot reviewed Oct 28, 2026

View reviewed changes

greptile-apps Bot reviewed Oct 28, 2026

View reviewed changes

SohamRatnaparkhi merged commit d9be0b6 into main Oct 28, 2026
9 checks passed

SohamRatnaparkhi deleted the auto/update-openapi-63732238aa1599bce293d1032ca8a9384146677d branch October 28, 2026 19:24

SohamRatnaparkhi mentioned this pull request Oct 28, 2026

docs(connectors): document ACL enforcement (PRO-3222 PRO-3223) #334

Merged

Navigation Menu

Repository navigation

🤖 Auto-Update: API Documentation OpenAPI Spec - #343

🤖 Auto-Update: API Documentation OpenAPI Spec#343
SohamRatnaparkhi merged 1 commit into
mainfrom
auto/update-openapi-63732238aa1599bce293d1032ca8a9384146677d

SohamRatnaparkhi commented Oct 28, 2026 •

edited by blacksmith-sh Bot

Loading

Uh oh!

mintlify Bot commented Oct 28, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 28, 2026

Uh oh!

openhack-agent Bot commented Oct 28, 2026

Uh oh!

openhack-agent Bot left a comment

Uh oh!

greptile-apps Bot commented Oct 28, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot Oct 28, 2026

Uh oh!

greptile-apps Bot Oct 28, 2026

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

SohamRatnaparkhi commented Oct 28, 2026 • edited by blacksmith-sh Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mintlify Bot commented Oct 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Oct 28, 2026

✅ Mintlify Hygiene

Uh oh!

openhack-agent Bot commented Oct 28, 2026

✅ OpenHack Summary

Confidence Score: 5/5

Uh oh!

openhack-agent Bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot commented Oct 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Confidence Score: 4/5

Findings

Summary

Uh oh!

greptile-apps Bot Oct 28, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Oct 28, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

SohamRatnaparkhi commented Oct 28, 2026 •

edited by blacksmith-sh Bot

Loading

mintlify Bot commented Oct 28, 2026 •

edited

Loading

greptile-apps Bot commented Oct 28, 2026 •

edited

Loading