Skip to content

Fix nesting of response/metadata in CheckPermission audit log example#565

Merged
julianleonard123 merged 1 commit into
authzed:mainfrom
julianleonard123:fix-formatting-on-audit-logs-docs
Jun 29, 2026
Merged

Fix nesting of response/metadata in CheckPermission audit log example#565
julianleonard123 merged 1 commit into
authzed:mainfrom
julianleonard123:fix-formatting-on-audit-logs-docs

Conversation

@julianleonard123

Copy link
Copy Markdown
Contributor

Summary

In the Audit Logging docs, the CheckPermission JSON example incorrectly nested the response and metadata fields inside the request object.

Per the Audit proto, request, response, error, and metadata are sibling fields:

message Audit {
  google.protobuf.Any request = 1;
  google.protobuf.Any response = 2;
  google.protobuf.Any error = 3;
  map<string, string> metadata = 4;
}

This now matches the correctly-formatted ReadSchema example directly below it.

🤖 Generated with Claude Code

@github-actions

github-actions Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Preview deployment status for this pull request.

Name Status Preview Updated (UTC)
docs 🟢 Ready Visit Preview Jun 29, 2026 06:06pm

The response and metadata fields were incorrectly nested inside the
request object. Per the Audit proto, request, response, error, and
metadata are sibling fields, as shown in the ReadSchema example.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@julianleonard123 julianleonard123 merged commit 57aca17 into authzed:main Jun 29, 2026
8 of 9 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 29, 2026
@julianleonard123 julianleonard123 deleted the fix-formatting-on-audit-logs-docs branch June 29, 2026 18:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants