liveBook · Manning

decK

As explained in Automating API Delivery

decK is a command-line tool for declaratively managing and synchronizing Kong Gateway configuration and detecting configuration drift.

decK manages Kong Gateway configuration declaratively: a repository stores the desired state, while decK validates it, synchronizes it to a Kong cluster, and helps detect drift. section 9.4.5

A practical deployment workflow is:

  • Run integration and API-conformance tests afterward to verify routing and definition compliance. section 9.4.5

Product Catalog routing

A Kong state file declares an HTTP Product Catalog service at product-api:8080 and routes GET requests matching ~/v1/catalog/products/(.+)$ without stripping the path.

How Automating API Delivery covers it

How deep it goes
Shows installation, state validation, synchronization, and post-deployment testing, but does not detail decK internals.
Examples
Uses Kong YAML for Product Catalog routing and GitHub Actions commands targeting Kong’s Admin API.
What it assumes
Assumes a Kong Gateway instance, a Kong state file, and basic CI runner scripting; supplies the decK installation step.
What you can do after
Operate/configure Kong Gateway declaratively through validated and synchronized state files in CI.
How it connects
Connects declarative configuration with Kong Gateway, configuration drift, CI/CD, and API conformance testing.
Cover of Automating API Delivery
liveBookmanning.com
Read Automating API Delivery on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.