You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…2072)
## Why make this change?
- Closes#2045. Any time that CosmosDB is the configured database, the
codepath that attempts to init the OpenAPI documentor service is run and
will always fail for CosmosDB. As a result, a "Fail" message always
appears on the console which can be misinterpreted as a user fixable
error and is a false positive notification of an issue.
## What is this change?
- OpenAPI documentor service init only occurs for non-CosmosDB database
types because db types like MSSQL , PG, MySQL are the only db types that
support the REST endpoint in DAB.
## How was this tested?
- [x] Run DAB with CosmosDB set as db type and ensure OpenAPI init
failure is not logged to console.
![image](https://github.com/Azure/data-api-builder/assets/6414189/39e2f41a-6f8d-44d9-8ae8-ee649f20ffa4)
What happened?
A bug happened!
Cosmos doesn't support openapi/rest so there should be no reference to openapi in dab logs when using cosmos.
Version
main
What database are you using?
CosmosDB NoSQL
What hosting model are you using?
Local (including CLI)
Which API approach are you accessing DAB through?
GraphQL
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: