7 Commits

Author	SHA1	Message	Date
Anton Averchenkov	3f073ae3ce	Revert "Add mount path into the default generated openapi.json spec (#17926)" (#18617) ... * Revert "Add mount path into the default generated openapi.json spec (UI) (#17926)" This reverts commit db8efac708. * Revert "Remove `generic_mount_paths` field (#18558)" This reverts commit 79c8f626c5.	2023-01-10 11:16:59 -05:00
Anton Averchenkov	db8efac708	Add mount path into the default generated openapi.json spec (UI) (#17926)	2022-12-08 12:15:54 -05:00
Anton Averchenkov	5b04a05511	Add logic to generate openapi response structures (#18192)	2022-12-05 11:11:06 -05:00
Anton Averchenkov	20f66ef7dd	Revert "Add mount path into the default generated openapi.json spec (#17839)" (#17890) ... This reverts commit 02064eccb4.	2022-11-10 15:39:53 -08:00
Anton Averchenkov	02064eccb4	Add mount path into the default generated openapi.json spec (#17839) ... The current behaviour is to only add mount paths into the generated `opeanpi.json` spec if a `generic_mount_paths` flag is added to the request. This means that we would have to maintain two different `openapi.json` files, which is not ideal. The new solution in this PR is to add `{mount_path}` into every path with a default value specified: ```diff -- "/auth/token/accessors/": { ++ "/auth/{mount_path}/accessors/": { "parameters": [ { "name": "mount_path", "description": "....", "in": "path", "schema": { "type": "string", ++ "default": "token" } } ], ``` Additionally, fixed the logic to generate the `operationId` (used to generate method names in the code generated from OpenAPI spec). It had a bug where the ID had `mountPath` in it. The new ID will look like this: ```diff -- "operationId": "listAuthMountpathAccessors", ++ "operationId": "listTokenAccessors", ```	2022-11-10 15:44:43 -05:00
Anton Averchenkov	dcb5942bd1	Change OpenAPI code generator to extract request objects (#14217)	2022-03-11 19:00:26 -05:00
Jeff Mitchell	170521481d	Create sdk/ and api/ submodules (#6583)	2019-04-12 17:54:35 -04:00