1
Allow usage of server variables other than default
Source: Kong/insomnia#4183 · opened by @meesvandongen
Is your feature request related to a problem? Please describe.
I would like to generate a Kong Configuration for multiple servers using the same OpenAPI specification file.
Describe the solution you'd like
OpenAPI allows specifying "server variables" in the servers field of the specification. These are currently set to the default value by openapi-2-kong. I would propose adding a new command line option to the CLI for specifying these server variables.
Describe alternatives you've considered
Writing a script to replace these variables in the generated config, perhaps substituting with another templating system so it doesn't interfere with openapi-2-kong.
Additional context
An example of a server variable in OpenAPI
I would like to generate a Kong Configuration for multiple servers using the same OpenAPI specification file.
Describe the solution you'd like
OpenAPI allows specifying "server variables" in the servers field of the specification. These are currently set to the default value by openapi-2-kong. I would propose adding a new command line option to the CLI for specifying these server variables.
Describe alternatives you've considered
Writing a script to replace these variables in the generated config, perhaps substituting with another templating system so it doesn't interfere with openapi-2-kong.
Additional context
An example of a server variable in OpenAPI
No pledges yet. Be the first to back this.
Comments
Similar requests
Redesign the environment variables
1 vote · 0 comments
Collection Specific Environment Variables Superseding Active Environment Variables
2 votes · 0 comments
Allow Environment variables as command line params to inso cli
7 votes · 0 comments
JSONPath/XPath access to Environment Variables
1 vote · 0 comments
Right Click Set Environment Variables
2 votes · 0 comments
No comments yet.