deck1

Configuration management for kong and kong enterprise

Overview

decK helps you manage Kong clusters with a declarative configuration file.

It can be used to export, import or sync entities to Kong.

`completion`	Generate the autocompletion script for the specified shell
`diff`	Diff the current entities in Kong with the on on disks
`dump`	Export Kong configuration to a file
`help`	Help about any command
`ping`	Verify connectivity with Kong
`reset`	Reset deletes all entities in Kong
`sync`	Sync performs operations to get Kong's configuration to match the state file
`validate`	Validate the state file
`version`	Print the version of decK

--ca-cert string: Custom CA certificate to use to verify Kong's Admin TLS certificate. This value can also be set using DECK_CA_CERT environment variable.

--headers strings: HTTP Headers(key:value) to inject in all requests to Kong's Admin API. This flag can be specified multiple times to inject multiple headers.

--kong-addr string: HTTP Address of Kong's Admin API. This value can also be set using DECK_KONG_ADDR

--skip-workspace-crud: Skip API calls related to Workspaces (Kong Enterprise only)

--tls-server-name string: Name to use to verify the hostname in Kong's Admin TLS certificate. This value can also be set using DECK_TLS_SERVER_NAME environment variable.

--tls-skip-verify: Disable verification of Kong's Admin TLS certificate. This value can also be set using DECK_TLS_SKIP_VERIFY environment variable.

--verbose int: Enable verbose verbose logging levels Setting this value to 2 outputs all HTTP requests/responses between decK and Kong.

Use "deck [command] --help" for more information about a command.

3 releases since Debian 11 (Bullseye); the text changed 2 times.