Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / kong/openapi2kong issues and pull requests

#24 - openapi2kong learnservice_oas.yaml fails on MacOS

Issue - State: open - Opened by tomereli 7 months ago - 2 comments

#23 - docs(example): fix example schema to be valid

Pull Request - State: closed - Opened by Tieske about 1 year ago

#22 - Unable to successfully perform "deck sync" with converted OAS definition file

Issue - State: closed - Opened by aldredb over 1 year ago - 1 comment

#21 - Create Consumers via Open API Spec

Issue - State: closed - Opened by neo-youre-pena over 1 year ago - 2 comments

#20 - chore(license) add Apache License

Pull Request - State: closed - Opened by kikito over 2 years ago

#19 - chore(cli) add deprecation warning

Pull Request - State: closed - Opened by Tieske over 3 years ago

#18 - Bump to 0.2.3

Pull Request - State: closed - Opened by eskerda almost 4 years ago

#18 - Bump to 0.2.3

Pull Request - State: closed - Opened by eskerda almost 4 years ago

#17 - fix(servers) servers block is optional

Pull Request - State: closed - Opened by Tieske almost 4 years ago

#17 - fix(servers) servers block is optional

Pull Request - State: closed - Opened by Tieske almost 4 years ago

#16 - generated security plugins are not tagged

Issue - State: open - Opened by Tieske almost 4 years ago

#16 - generated security plugins are not tagged

Issue - State: open - Opened by Tieske almost 4 years ago

#15 - "servers" should be optional

Issue - State: open - Opened by Tieske almost 4 years ago

#14 - chore(*) bump version due to copyright header additions

Pull Request - State: closed - Opened by mikefero about 4 years ago

#14 - chore(*) bump version due to copyright header additions

Pull Request - State: closed - Opened by mikefero about 4 years ago

#13 - chore(*) add copyright

Pull Request - State: closed - Opened by kidd about 4 years ago

#13 - chore(*) add copyright

Pull Request - State: closed - Opened by kidd about 4 years ago

#12 - recursive JSONschema support

Issue - State: open - Opened by Tieske over 4 years ago

#12 - recursive JSONschema support

Issue - State: open - Opened by Tieske over 4 years ago

#11 - fix(registry) values should not be weak

Pull Request - State: closed - Opened by Tieske almost 5 years ago

#11 - fix(registry) values should not be weak

Pull Request - State: closed - Opened by Tieske almost 5 years ago

#10 - Fix/body validation

Pull Request - State: closed - Opened by Tieske almost 5 years ago - 2 comments

#10 - Fix/body validation

Pull Request - State: closed - Opened by Tieske almost 5 years ago - 2 comments

#9 - fix(example) use proper 'x-' extension

Pull Request - State: closed - Opened by Tieske almost 5 years ago

#9 - fix(example) use proper 'x-' extension

Pull Request - State: closed - Opened by Tieske almost 5 years ago

#8 - option to force unique names

Issue - State: open - Opened by Tieske about 5 years ago

#8 - option to force unique names

Issue - State: open - Opened by Tieske about 5 years ago

#7 - Multiple auth not yet supported

Issue - State: open - Opened by aaronhmiller about 5 years ago

#7 - Multiple auth not yet supported

Issue - State: open - Opened by aaronhmiller about 5 years ago

#6 - use redirects for http+https servers

Issue - State: closed - Opened by Tieske about 5 years ago - 2 comments

#6 - use redirects for http+https servers

Issue - State: closed - Opened by Tieske about 5 years ago - 2 comments

#5 - add multiple auth; AND/OR schemes

Issue - State: open - Opened by Tieske about 5 years ago

#5 - add multiple auth; AND/OR schemes

Issue - State: open - Opened by Tieske about 5 years ago

#4 - feat(log) add a source-trace to the error messages

Pull Request - State: closed - Opened by Tieske about 5 years ago

#3 - Error when upstream server unreachable

Issue - State: open - Opened by aaronhmiller about 5 years ago - 2 comments

#3 - Error when upstream server unreachable

Issue - State: open - Opened by aaronhmiller about 5 years ago - 2 comments

#2 - enhance error message with "stack trace" to yaml element

Issue - State: closed - Opened by Tieske about 5 years ago

#2 - enhance error message with "stack trace" to yaml element

Issue - State: closed - Opened by Tieske about 5 years ago

#1 - add x-kong-route-defaults to docs

Issue - State: closed - Opened by Tieske about 5 years ago

#1 - add x-kong-route-defaults to docs

Issue - State: closed - Opened by Tieske about 5 years ago