target-bind

Bind Units to Targets for delivery destinations and guardrails before apply.

2|2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/confighub/confighub-skills --skill target-bind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: target-bind
Source: https://github.com/confighub/confighub-skills/tree/main/skills/target-bind
Command: npx skills add https://github.com/confighub/confighub-skills --skill target-bind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Binding Units to a Destination ensures you can specify where configurations land before an apply, reducing misrouting and enabling reuse of delivery targets.

Core Features & Use Cases

  • Create or update a Target with provider/toolchain and parameter JSON, so Units know where to land.
  • Attach one or more Units to that Target, supporting single-unit or bulk binding.
  • Validate compatibility and verify binding state with cub commands before proceeding to cub-apply.

Quick Start

Bind the checkout unit to the prod Kubernetes target in the app-space and verify the binding is established.

Frequently Asked Questions about target-bind

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

FAQPage Schema
How do I bind configuration units to a Kubernetes deployment target?

Bind configuration units to a Kubernetes target by creating or updating the target with provider parameters, then attaching the units using the set-target command. This specifies delivery destinations and guardrails before applying configurations.

Can I bulk bind multiple units to a single delivery target across different spaces?

Yes, bulk binding multiple units to a single target is supported across spaces and providers. You can attach one or more units to a target and verify the binding state across the deployment environment before proceeding.

How do I verify a unit binding is established before running an apply?

Verify a unit binding by running the target get and unit get commands. These validation checks confirm compatibility and ensure the binding state is correctly established before you proceed to apply configurations.

How do I update an existing Kubernetes target with new parameters?

Update an existing Kubernetes target by running the target update command with new provider and parameter JSON. This modifies the delivery destination settings while maintaining safety checks to prevent unintended deployments.

Why do I need to bind units to a target before applying configurations?

Binding units to a target before applying configurations ensures you specify exactly where configurations land. This reduces misrouting risks and enables the reuse of delivery targets across your deployment workflow.

Does unit binding work with alternative renderers and non-Kubernetes providers?

Yes, unit binding works with Kubernetes targets and alternative renderers across various providers. The process supports updating existing targets and validating compatibility regardless of the specified delivery destination.