kl provider

kl provider manages stored provider configuration blocks.

Use it when provider-driven workflows need provider config to exist in KiloLock-managed storage instead of only in local Terraform context.

Subcommands

• configure
• get
• list
• remove

Meaningful examples

Store a provider configuration from JSON

cat provider.json | kl provider configure hashicorp/aws --from-json -

Use this when you want a provider config block recorded for later backend-driven workflows.

Read one stored provider config

kl provider get hashicorp/aws

Use this to verify what is currently stored before a refresh or operator repair workflow.

List provider configs

kl provider list

Good for auditing what provider sources and aliases are available.

Remove one stored provider config

kl provider remove hashicorp/aws

Use this when cleaning up stale or incorrect provider definitions.

Source address forms

Examples from the CLI:

• null
• hashicorp/aws
• registry.terraform.io/hashicorp/aws

Notes

• Provider config management is not the first command most teams need.
• It becomes important once refresh and other provider-driven workflows are part of normal operations.