-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem: Pulp's OpenAPI schema has verbose Operation Ids #178
Conversation
Solution: request OpenAPI schema with 'bindings' query parameter This patch takes advantage of a new feature in pulpcore that allows generating OpenAPI schema with short Operation Ids. Required PR: pulp/pulpcore#178 re: #4989 https://pulp.plan.io/issues/4989
3e637ea
to
3d0be48
Compare
Codecov Report
@@ Coverage Diff @@
## master #178 +/- ##
==========================================
- Coverage 67.33% 67.05% -0.29%
==========================================
Files 65 65
Lines 3089 3102 +13
==========================================
Hits 2080 2080
- Misses 1009 1022 +13
Continue to review full report at Codecov.
|
Solution: request OpenAPI schema with 'bindings' query parameter This patch takes advantage of a new feature in pulpcore that allows generating OpenAPI schema with short Operation Ids. Required PR: pulp/pulpcore#178 re: #4989 https://pulp.plan.io/issues/4989
2013eb0
to
a04afb9
Compare
Solution: request OpenAPI schema with 'bindings' query parameter This patch takes advantage of a new feature in pulpcore that allows generating OpenAPI schema with short Operation Ids. Required PR: pulp/pulpcore#178 re: #4989 https://pulp.plan.io/issues/4989
a04afb9
to
e5e18fe
Compare
I like the resulting bindings. |
Yes, even if it is called the same thing, the object is provided by a different package. |
e5e18fe
to
aaeea9f
Compare
Solution: add ability to request shorter operation ids in the schema This patch adds ability to specify 'bindings' query parameter when requesting the OpenAPI schema. When specified, a short OperationId is used for each operation. This patch also changes how the OpenAPI schema operations are grouped together. Each resource now has its own tag associated with it. This results in better REST API docs and better experience for users of bindings. The tag for a resource is determined from it's URL. The plugin name is omitted from the tag. For example: URL: /pulp/api/v3/repositories/ Tag: Repositories URL: /pulp/api/v3/repositories/<uuid>/versions/ Tag: Repositories: Versions URL: /pulp/api/v3/content/file/files/ Tag: Content: Files URL: /pulp/api/v3/remotes/file/file/ Tag: Remotes: File Required PR: pulp/pulp-openapi-generator#18 re: pulp#4989 https://pulp.plan.io/issues/4989
aaeea9f
to
7748ffd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all makes sense to me.
Solution: add ability to request shorter operation ids in the schema
This patch adds ability to specify 'bindings' query parameter when requesting the OpenAPI
schema. When specified, a short OperationId is used for each operation.
This patch also changes how the OpenAPI schema operations are grouped together. Each resource
now has its own tag associated with it. This results in better REST API docs and better
experience for users of bindings.
The tag for a resource is determined from it's URL. The plugin name is omitted from the tag. For
example:
URL: /pulp/api/v3/repositories/
Tag: Repositories
URL: /pulp/api/v3/repositories/uuid-of-some-sort/versions/
Tag: Repositories: Versions
URL: /pulp/api/v3/content/file/files/
Tag: Content: Files
URL: /pulp/api/v3/remotes/file/file/
Tag: Remotes: File
Required PR: pulp/pulp-openapi-generator#18
re: #4989
https://pulp.plan.io/issues/4989