How to manage in a CI/CD pipeline an InterSystems API Manager (IAM aka Kong GATEWAY) configuration ?

Kong provides an open source configuration management tool (written in Go), called decK (which stands for declarative Kong)

• Check that decK recognizes your Kong Gateway installation via deck ping

deck ping   
Successfully connected to Kong!
Kong version:  2.3.3.2-enterprise-edition

• Export Kong Gateway configuration to a file named "kong.yaml" via deck dump

deck dump

• After modifying the kong.yaml, show the differences via deck diff

deck diff
updating service alerts  {
   "connect_timeout": 60000,
-  "host": "172.24.156.176",
+  "host": "192.10.10.18",
   "id": "3bdd7db4-0b75-4148-93b3-2ff11e961f64",
   "name": "alerts",
   "path": "/alerts",
   "port": 50200,
   "protocol": "http",
   "read_timeout": 60000,
   "retries": 5,
   "write_timeout": 60000
 }

Summary:
  Created: 0
  Updated: 1
  Deleted: 0

• Apply changes via deck sync

deck sync
updating service alerts  {
   "connect_timeout": 60000,
-  "host": "172.24.156.176",
+  "host": "192.10.10.18",
   "id": "3bdd7db4-0b75-4148-93b3-2ff11e961f64",
   "name": "alerts",
   "path": "/alerts",
   "port": 50200,
   "protocol": "http",
   "read_timeout": 60000,
   "retries": 5,
   "write_timeout": 60000
 }

Summary:
  Created: 0
  Updated: 1
  Deleted: 0

deck sync -s workspace1.yaml --workspace workspace1

deck sync -s workspace2.yaml --workspace workspace2

For more information :

https://docs.konghq.com/deck/1.11.x/guides/getting-started/

https://docs.konghq.com/deck/1.11.x/guides/best-practices/