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

[management-api] Error 500 when creating a new API from Swagger descriptor #454

Closed
anchsu opened this Issue Feb 16, 2017 · 0 comments

Comments

Projects
None yet
3 participants
@anchsu

anchsu commented Feb 16, 2017

Current Behavior

Choose "Import Swagger descriptor" when creating a new API.
Select Inline (from local file-system) or URL
If the json don't contains "schemes" we have an error 500.
In the swagger specification this field isn't mandatory :
"The transfer protocol of the API. Values MUST be from the list: "http", "https", "ws", "wss". If the schemes is not included, the default scheme to be used is the one used to access the Swagger definition itself."

Possible Solution

When import the swagger definition, use the scheme of swagger url used to import the file.

@brasseld brasseld self-assigned this Feb 16, 2017

@brasseld brasseld added the type: bug label Feb 16, 2017

@brasseld brasseld added this to the 1.4.0 milestone Feb 16, 2017

@brasseld brasseld changed the title from [management-api] error 500 when creating a new API to [management-api] Error 500 when creating a new API from Swagger descriptor Feb 16, 2017

brasseld added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Feb 16, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Feb 17, 2017

@NicolasGeraud NicolasGeraud modified the milestones: 1.3.3, 1.4.0 Feb 17, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment