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

core: support configurable openapi URLs #488

Closed
bajtos opened this issue Aug 4, 2017 · 5 comments
Closed

core: support configurable openapi URLs #488

bajtos opened this issue Aug 4, 2017 · 5 comments

Comments

@bajtos
Copy link
Member

bajtos commented Aug 4, 2017

Allow application developers to customize the URL where application's openapi spec is served (current hard-coded default: /openapi.json).

See #475 (comment)

@raymondfeng
Copy link
Contributor

To serve OpenAPI spec with LB.next will be a good a validation for the following perspectives:

  1. Allow a component (openapi explorer component) to serve certain routes
  2. Support content negations based on Accept header and other information so that we can render OpenAPI spec in v2, v3, json, yaml etc.
  3. Enable CORS

@stale
Copy link

stale bot commented May 1, 2018

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label May 1, 2018
@dhmlau dhmlau removed the stale label May 10, 2018
@bajtos bajtos added post-GA and removed LB4 GA labels Jul 23, 2018
@bajtos
Copy link
Member Author

bajtos commented Jul 23, 2018

Removing from 4.0 GA to "Further rest layer improvements" epic (#1452).

@dhmlau dhmlau removed the non-DP3 label Aug 23, 2018
@dhmlau dhmlau removed the post-GA label Nov 2, 2018
@stale
Copy link

stale bot commented Oct 28, 2019

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Oct 28, 2019
@stale
Copy link

stale bot commented Nov 27, 2019

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Nov 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants