Hello, I am running a kong installation (currently 1.0.1) with a number of services, routes, plugins, etc. I would like to upgrade to 1.1 using DB-less/declarative config. But I would like to avoid to manually code every configuration I have done so far because this would be much work and rather error-prone. Is there a good way of migration? E.g. a kong dump config command that reads the DB config and writes the corresponding new declarative config. This does not need to be fully perfect. A starting point for manually checking and adapting would be very helpful. Any ideas? Thank you very much.

Yes. Using decK instead of the 1.1-declarative config would not have the problem. But that’s not what I’d prefer… Doesn’t anybody else want to migration from kong DB to DB-less?

@dsteinkopf You can use deck dump to output a kong.yaml file, which will contain all your entities from Kong’s database. The YAML file generated is compatible with Kong 1.1 declarative configuration file. You simply have to add the following line at to the YAML file and everything should work: _format_version: "1.1"

Oh, sounds great. Thank you very much for making that clear. I’ll try that. So deck is compatible to the Kong 1.1. decl. config file? (If yes: Maybe you should mention this fact in https://github.com/hbagdi/deck#compatibility)

Migrate from DB to DB-less/declarative config

Questions

mgkong June 12, 2019, 7:58pm 2

decK would be the ideal solution in this case: decK: declarative configuration for Kong

Topic		Replies	Views
Declarative config with a database Questions	8	3704	July 29, 2019
Declarative config General	5	1439	July 31, 2019
Moving kong configuration from dev to prod cluster Questions	8	1580	July 24, 2019
decK: declarative configuration for Kong General kong-gateway	8	4953	April 9, 2019
Kong 1.1.0rc1 available for testing General	13	3136	March 22, 2019

Migrate from DB to DB-less/declarative config

Related topics