Skip to content
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

support specific swagger or openapi security and validator configuration #45

Closed
stevehu opened this issue Aug 12, 2018 · 0 comments
Closed

Comments

@stevehu
Copy link
Contributor

stevehu commented Aug 12, 2018

Previously, each service instance can only support one chain of middleware handlers and that means you can only choose one framework per instance. With the multiple chain support introduced in 1.5.17, we can have multiple frameworks in the same instance. For example, both swagger and openapi in the same instance with different specifications for v1 and v2. OpenAPI and GraphQL support in the same instance etc. To support the new feature, we need to separate the security and validator config files in case different frameworks have different configurations. For backward compatibility, the generic shared security.yml and validator.yml are still used if all frameworks are sharing the same config or there is only one framework available on the server instance.

The logic is to use framework specific config {framework}-security.yml or {framework}-validator.yml first and then fallback to security.yml or validator.yml

stevehu added a commit that referenced this issue Aug 12, 2018
stevehu added a commit that referenced this issue Aug 12, 2018
fixes #45 support specific swagger or openapi security and validator …
stevehu added a commit that referenced this issue Aug 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant