You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I imported into API Gateway a Swagger definition using your importer tool.
A small snippet of a path 👍
paths:
'/service/{cluster-id}':
parameters:
- name: 'cluster-id'in: pathtype: stringformat: uint64required: truedescription: The ID of the cluster as an unsigned long decimal stringpost:
tags:
- serviceconsumes:
- application/jsonproduces:
- application/jsonparameters:
- in: bodyname: bodyrequired: trueschema:
$ref: '#/definitions/registerServiceRequest'responses:
'200':
description: Successschema:
$ref: '#/definitions/registerServiceResponse''406':
description: Error 406
When its exported using either the AWS Export GUI or your tool the path parameter definitions are gone. I realize there is no direct equivalent in API Gateway (except the Path mapping for HTTP integrations), and there is no schema for them. But I was hoping that an import then export might round trip well enough to be usable.
As it is now paths with /{param} but no parameters declarations dont parse in swagger.
I tried using global parameter defs, path and operation parameters and none show up in the output.
example:
( Note a truncated path -- I will file a separate issue)
Unfortunately almost all of definition info for path parameters (same for query parameters and header parameters) is lost when imported into API Gateway. It keeps "required" flag only (and obviously "in").
I imported into API Gateway a Swagger definition using your importer tool.
A small snippet of a path 👍
When its exported using either the AWS Export GUI or your tool the path parameter definitions are gone. I realize there is no direct equivalent in API Gateway (except the Path mapping for HTTP integrations), and there is no schema for them. But I was hoping that an import then export might round trip well enough to be usable.
As it is now paths with /{param} but no parameters declarations dont parse in swagger.
I tried using global parameter defs, path and operation parameters and none show up in the output.
example:
( Note a truncated path -- I will file a separate issue)
The text was updated successfully, but these errors were encountered: