azure / data-api-builder Goto Github PK

Given GraphQL schema, Data Gateway should be able to generate select query implicitly.

System.Text.Json seems to have limited abilities in terms of writing/creating a JsonDocument. So we need migrate the runtime to use Newtonsoft.Json instead of System.Text.Json to achieve the relevant functionalities like creating JArray with elements etc.

Point lookup by Id/primary key for select,update,insert

Simple Query with filter (no perf expectation, and no pagination)

Due to complexity in implementation in CosmosDB, this will also be in M1.

Verify PrimaryKey field names sent in the url match the ones obtained from the table schema

See this RFP: https://github.com/Azure/project-hawaii/issues/11

Today we have a FileMetadataProvider.
Implement a DatabaseMetadataProvider that reads the schema from database and fills in the same config values that we do today using the FileMetadataProvider.
The goal would be to get to a point where we can run all tests using either the File or the DatabaseMetadataProvider

Docker container should not be shipped with a config file. We need to specify the location of config file that Data Gateway should look for. Either via environment variable or using well-known path when mount docker volume that contains config file.

Simple public, authenticated, or none authorization

See this RFP : https://github.com/Azure/project-hawaii/issues/11

Allow specifiying something like a --watch to make the runtime watch the provided configs and reload when they change.

Relevant comment from @jarupatj in #50:

You should look at using IOptionsMonitor
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options?view=aspnetcore-5.0#options-interfaces

#892

Only for point look up by Id/primary key