I created an API proxy from Open API doc as below -
'/users/{user_ids}': get: tags: - onboarding summary: >- Verify if a user exists either in context to the mobile platform, the HRMS or the CHMS. description: >- This operation checks if the user exists in each of the end systems and accordingly responds with the enumerated key in it's response. The chronological order of it's check is first Mobile Platform, then HRMS and then CHMS. operationId: fetchUsers produces: - application/json parameters: - name: user_ids type: string in: path description: >- Required. Comma separated string of user identifiers with a limit of 20 ids. required: true responses: '200': description: Successfully fetched username. schema: $ref: '#/definitions/FetchUsersResponse'
When i try to generate the Open API doc from the API proxy using the apigee2openapi tool, the 'parameters' tag was missing in the generated document as below -
"/users/*": { "get": { "operationId": "fetchUsers", "summary": "Verify if a user exists either in context to the mobile platform, the HRMS or the CHMS.", "responses": { "200": { "description": "successful operation" } } } }
Please help me in resolving this.
I think you are trying to "round trip" between the spec and the API Proxy, and that's not supported by the apigee2openapi tool.
Actually my point is when i generate open API spec through the apigee2openapi tool, i do not get the parmaters tag. I tried with the petstore example also that is used to explain the tool.
In the generated spec from the proxy, they have shown the parameter tag but that does not happen when i generated the spec using the tool.
I just want to ask how to make sure that 'parameters' tag is available in the generated spec.