Issues getting REST endpoints to work with child data source configurations

[pontiusmatt]

I am trying to get REST endpoints exposed through a single DAB instance that has child configurations for multiple database connections. When I do this per the documentation, the entities defined in the configuration in the child configs end up not setting up correctly for rest endpoints even if i define the methods they should get. The logs do not seem to be super helpful, it looks like it sets up correctly, but when I go to the swagger endpoint to inspect the endpoints the entity shows, but with no methods under it.

I am wondering if I am doing something not supported here, or if anyone out there has this functionality working?

[aaronburtle]

I am trying to get REST endpoints exposed through a single DAB instance that has child configurations for multiple database connections. When I do this per the documentation, the entities defined in the configuration in the child configs end up not setting up correctly for rest endpoints even if i define the methods they should get. The logs do not seem to be super helpful, it looks like it sets up correctly, but when I go to the swagger endpoint to inspect the endpoints the entity shows, but with no methods under it.

I am wondering if I am doing something not supported here, or if anyone out there has this functionality working?

Thanks for raising this pontiusmatt . Multiple-database REST endpoints are supported, but Swagger/OpenAPI currently has a known limitation with entities from child configurations. The OpenAPI document is built from the default/root data source’s metadata, so a child entity can appear as an empty Swagger group without any operations. This is tracked as issue #2462.

A couple of configuration details are worth checking:

1. For tables and views, rest.methods is ignored. Enable REST with rest.enabled, and control the available operations through the entity’s permissions: read, create, update, delete, or *.

2. rest.methods applies only to stored procedures, which also require the execute permission.

3. Global runtime settings come from the root configuration. A runtime section in a child configuration is ignored.

Please try calling the child entity directly, for example GET /api/. If that succeeds, the configuration is working and this is only the Swagger/OpenAPI limitation.