I set use_db_app_configs to false on purpose, I want to have as much configuration as possible done via json so that the stack can be instantiated from a repository, either in kubernetes or docker-compose. Name resolution is also done by the container.

The panic is caused because the API that you are trying to create the key for is not loaded in the gateway, this can happen for many reasons, the gateway boot-up log will show you if it exists or not, or why it was skipped. This panic has been fixed in the latest upcoming version, but even if this key was created, you would find that you would get a 404 if you used it too soon because the gateway has not yet made this API active.

You must either use the gateway in file-baed mode, or in dashboard mode, the two do not mix well and we don't really support it. In file-based mode everything must be done as a file on disk, and you do not need any of the settings for the gateway to register with the dashboard. So pick one and we can help