deck-cli

Manage Kong Gateway and Konnect configurations declaratively with the decK CLI.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/oliwynn-kong/deck-cli-skill --skill deck-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deck-cli
Source: https://github.com/oliwynn-kong/deck-cli-skill/tree/main
Command: npx skills add https://github.com/oliwynn-kong/deck-cli-skill --skill deck-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires deck, aws, curl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Managing and syncing Kong Gateway and Konnect configurations across environments is error-prone, manual, and difficult to automate; this skill provides a repeatable declarative workflow to validate, preview, convert, backup, and apply configuration state safely.

Core Features & Use Cases

  • Declarative configuration management for Kong Gateway and Konnect using the decK CLI.
  • Validate and lint local state files, preview changes with diffs, and apply or sync state with workspace and tag filtering.
  • Convert OpenAPI specs to Kong configuration, export current live state, detect configuration drift, and run safe deployments with backup and rollback support (CI/CD friendly).

Quick Start

Use the deck-cli skill to validate kong.yaml, preview differences against the live gateway, create a backup, and perform a safe sync to Kong or Konnect.

Frequently Asked Questions about deck-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Kong Gateway configurations declaratively?

You can manage Kong Gateway declaratively by using decK to validate state files, preview gateway diffs, and sync configurations safely. This approach allows you to apply state with workspace and tag filtering to ensure accurate environment synchronization.

Can I convert OpenAPI specs to Kong configuration files?

Yes, you can convert OpenAPI specs to Kong configuration. The decK CLI performs deterministic conversions, translating API definitions directly into declarative state files required to provision Kong Gateway routes and services.

What is the best way to detect configuration drift in Konnect?

The best way to detect configuration drift in Konnect is exporting the current live state and comparing it against your local declarative state files. decK provides diff capabilities to highlight discrepancies between intended and actual live configurations.

Do I need AWS credentials to backup Kong state files to S3?

Yes, you need AWS credentials to backup Kong state files to S3. The workflow supports optional S3 backups during CI/CD pipelines, requiring the AWS CLI to be installed and properly authenticated to securely store your configuration state.

How do I sync Kong configurations safely in a CI/CD pipeline?

To sync Kong configurations safely in CI/CD, create a backup, preview changes with a diff, and perform a non-destructive apply or sync. This decK workflow ensures safe deployments with rollback support and optional S3 backups.

What is the difference between apply and sync semantics in decK?

The difference between apply and sync semantics in decK is that a non-destructive apply updates configurations without removing unspecified entities, while sync fully aligns the live gateway state with your declarative state files.