Custom entities migrations uses "postgresql" key instead of "postgres"

[bforbis]

Where is the problem?

https://docs.konghq.com/gateway/latest/plugin-development/custom-entities/

What happened?

The example migrations config is invalid, as kong expects the key to be "postgres" and not "postgresql".

The following error message is returned at startup:

subsystem is invalid: 4 schema violations (at least one of these fields must be non-empty: 'postgres.up', 'postgres.up_f', 'postgres.teardown', 'cassandra.up', 'cassandra.up_f', 'cassandra.teardown'; cassandra: required field missing; postgres: required field missing; postgresql: unknown field

What did you expect to happen?

Documentation should be correct

Code of Conduct and Community Expectations

• I agree to follow this project's Code of Conduct
• I agree to abide by the Community Expectations