This is an automated email from the ASF dual-hosted git repository.
jerryshao pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/gravitino.git
The following commit(s) were added to refs/heads/main by this push:
new e28a72c5f0 [MINOR] docs: state that supportedObjectTypes is not
enforced in the OpenAPI spec (#13758)
e28a72c5f0 is described below
commit e28a72c5f04f1c04fb2b113696be066774c21946
Author: Mark Hoerth <[email protected]>
AuthorDate: Sun Oct 11 21:22:07 2026 -0500
[MINOR] docs: state that supportedObjectTypes is not enforced in the
OpenAPI spec (#13758)
The prose pages already say the field is declarative and that object
policy lookup does not filter by it, but docs/open-api/policies.yaml
still described it as the types the content "can be applied to", which
reads as a constraint the server enforces. The spec now matches the
prose.
Docs only, no behaviour change.
Co-authored-by: Claude <[email protected]>
---
docs/open-api/policies.yaml | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/docs/open-api/policies.yaml b/docs/open-api/policies.yaml
index ce5adcac28..3a1a943fb3 100644
--- a/docs/open-api/policies.yaml
+++ b/docs/open-api/policies.yaml
@@ -519,7 +519,11 @@ components:
properties:
supportedObjectTypes:
type: array
- description: The types of metadata objects this policy content can
be applied to.
+ description: >-
+ Declares the metadata object types the policy's rules are intended
for. The field
+ is not enforced: associating a policy does not check it, and
object policy lookup
+ does not filter by it. Consumers decide whether a policy type
applies to the
+ object they are processing.
minItems: 1
items:
type: string
