-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Move enable_swagger_ui config to api #50896
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
Move enable_swagger_ui config to api #50896
Conversation
c055ba0 to
b272e7a
Compare
|
Static check failing on the hash of the fab compile assets. Can save time without checking the logs |
b272e7a to
b44f08e
Compare
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 7d69f2e v3-0-testThis should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
* Move enable_swagger_ui config to api * Fix CI (cherry picked from commit 7d69f2e)
|
Manual backport #50946 |
* Move enable_swagger_ui config to api * Fix CI (cherry picked from commit 7d69f2e)
* Move enable_swagger_ui config to api * Fix CI (cherry picked from commit 7d69f2e)
* Move enable_swagger_ui config to api * Fix CI
* Move enable_swagger_ui config to api * Fix CI
Closes: #49896
Last one of the ticket.
webserverconfig section is almost dead, there's only 3 config options remaining that should probably get killed too.