Is your feature request related to a problem? Please describe.
Some of the configuration parameters seem unnecessarily restrictive.
the OpenAPI spec needs to be obtained from the same endpoint as the API because the parameter swagger_file is always prefixed with the url parameter (see here)
the auth token needs to be obtained from the same endpoint as the API because the get_token/url_complement parameter is always prefixed with the url parameter (see here)
Describe the solution you'd like
Could we interpret the parameters swagger_file and get_token/url_complement as full URLs instead and not prefix them with url? This would be a breaking change.
Describe alternatives you've considered
Alternatively there could be an additional logic that checks if the parameters are relative paths and only then prefixes them with the url parameter. This would be backwards compatible.
url - Endpoint URL. e.g. https://example.com
swagger_file - Route for access to the swagger file. e.g. openapi.json
get_token/url_complement - Retrieving a token from the endpoint.
// duplicates feature request
Is your feature request related to a problem? Please describe.
Some of the configuration parameters seem unnecessarily restrictive.
swagger_fileis always prefixed with theurlparameter (see here)get_token/url_complementparameter is always prefixed with theurlparameter (see here)Describe the solution you'd like
Could we interpret the parameters
swagger_fileandget_token/url_complementas full URLs instead and not prefix them withurl? This would be a breaking change.Describe alternatives you've considered
Alternatively there could be an additional logic that checks if the parameters are relative paths and only then prefixes them with the
urlparameter. This would be backwards compatible.Additional context
docs