Schema validation in db-less mode Kong 1.4

[altexy]

Summary

Schema validation silently ignored when starting Kong in db-less mode.

Steps To Reproduce

1. Write db-less config with any plugin with missed required field.
2. Start Kong in DB-less mode

Kong 1.3.x failed to start, the error log contains an appropriate message.

Kong 1.4.x silently start, no schema validation logs present.

Additional Details & Logs

• Kong version official Docker images kong:1.4.x-alpine and kong:1.3.x-alpine

[bungle]

@altexy, thanks for reporting. Possibly a bug.

[bungle]

@hishamhm, do you have an idea about this?

[hbagdi]

Re-opening because https://discuss.konghq.com/t/kong-2-0-1-db-less-schema-validation-issue/6375

[bungle]

I can confirm that this only happens with reload. So investigating it further.

E.g. start with:

_format_version: "1.1"

services:
  - name: sample_api
    host: kong.test
    port: 4000

KONG_DATABASE=off KONG_DECLARATIVE_CONFIG=b.yaml ./bin/kong start --vv

And you have:

{
    "data": [
        {
            "client_certificate": null,
            "connect_timeout": 60000,
            "created_at": 1590998526,
            "host": "kong.test",
            "id": "f43346f0-16f5-55b3-b815-f4dfa7cdb1e8",
            "name": "sample_api",
            "path": null,
            "port": 4000,
            "protocol": "http",
            "read_timeout": 60000,
            "retries": 5,
            "tags": null,
            "updated_at": 1590998526,
            "write_timeout": 60000
        }
    ],
    "next": null
}

Then

_format_version: "1.1"

services:
  - name: sample_api
    port: 4000
  - name: sample_api2
    host: another.test
    port: 4000

KONG_DATABASE=off KONG_DECLARATIVE_CONFIG=b.yaml ./bin/kong reload --vv

And you have:

{
    "data": [
        {
            "client_certificate": null,
            "connect_timeout": 60000,
            "created_at": 1590998526,
            "host": "kong.test",
            "id": "f43346f0-16f5-55b3-b815-f4dfa7cdb1e8",
            "name": "sample_api",
            "path": null,
            "port": 4000,
            "protocol": "http",
            "read_timeout": 60000,
            "retries": 5,
            "tags": null,
            "updated_at": 1590998526,
            "write_timeout": 60000
        }
    ],
    "next": null
}

Also:

./bin/kong config parse b.yaml
Error: Failed parsing:
in 'services':
  - in entry 1 of 'services':
    in 'host': required field missing

  Run with --v (verbose) or --vv (debug) for more details

So I think that perhaps the reload does not load declarative and you actually need restart to do so? So is this expected or not? @hishamhm?

[bungle]

I think it is expected. reload does not honor environment vars it uses the env vars that were used when Kong was started.

[bungle]

I am closing this now. Please reopen if you have any further info, or need more guidance.