This is an automated email from the ASF dual-hosted git repository.
jshao 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 f4f07186b [#6080] fix(docs): Fix the wrong possible values. (#6084)
f4f07186b is described below
commit f4f07186b34c5d2e145783622a0d6f90b3004e69
Author: Cheng-Yi Shih <[email protected]>
AuthorDate: Fri Jan 3 15:30:00 2025 +0800
[#6080] fix(docs): Fix the wrong possible values. (#6084)
What changes were proposed in this pull request?
List role names for metadata object, "COLUMN" and "ROLE" value for
"metadataObjectType" are meaningless currently. Remove it.
Why are the changes needed?
Fix: #6080
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Just documents.
---
docs/open-api/roles.yaml | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/docs/open-api/roles.yaml b/docs/open-api/roles.yaml
index 986d0fdc6..5ce9c26ee 100644
--- a/docs/open-api/roles.yaml
+++ b/docs/open-api/roles.yaml
@@ -148,7 +148,7 @@ paths:
/metalakes/{metalake}/objects/{metadataObjectType}/{metadataObjectFullName}/roles:
parameters:
- $ref: "./openapi.yaml#/components/parameters/metalake"
- - $ref: "./openapi.yaml#/components/parameters/metadataObjectType"
+ - $ref: "#/components/parameters/metadataObjectTypeOfRole"
- $ref: "./openapi.yaml#/components/parameters/metadataObjectFullName"
get:
@@ -386,4 +386,19 @@ components:
value: {
"code": 0,
"names": [ "user1", "user2" ]
- }
\ No newline at end of file
+ }
+ parameters:
+ metadataObjectTypeOfRole:
+ name: metadataObjectType
+ in: path
+ description: The type of the metadata object
+ required: true
+ schema:
+ type: string
+ enum:
+ - "METALAKE"
+ - "CATALOG"
+ - "SCHEMA"
+ - "TABLE"
+ - "FILESET"
+ - "TOPIC"
\ No newline at end of file
