Add Kubefleet ClusterResourcePlacement template support and fix addon system

[Copilot]

This PR implements comprehensive support for Kubefleet's ClusterResourcePlacement manifests in Draft, enabling users to generate both PickAll and PickFixed placement type manifests as requested in the issue.

New Features

Kubefleet ClusterResourcePlacement Template

Added kubefleet-clusterresourceplacement addon template that supports:

• metadata.name configuration via CRP_NAME variable
• spec.resourceSelectors.name configuration via RESOURCE_SELECTOR_NAME variable
• policy.placementType configuration via PLACEMENT_TYPE variable (PickAll/PickFixed)
• policy.clusterNames configuration via CLUSTER_NAME_1 and CLUSTER_NAME_2 variables for PickFixed type
• Standard Draft labels and metadata patterns

Usage Examples

PickAll placement type:

draft update --addon kubefleet-clusterresourceplacement \
  --variable CRP_NAME=demo-crp \
  --variable RESOURCE_SELECTOR_NAME=fmad-demo \
  --variable PLACEMENT_TYPE=PickAll \
  --variable PARTOF=my-project

Generates the exact YAML from the first sample in the issue:

apiVersion: placement.kubernetes-fleet.io/v1
kind: ClusterResourcePlacement
metadata:
  name: demo-crp
  labels:
    app.kubernetes.io/name: demo-crp
    app.kubernetes.io/part-of: my-project
    kubernetes.azure.com/generator: draft
spec:
  resourceSelectors:
    - group: ""
      kind: Namespace
      name: fmad-demo
      version: v1
  policy:
    placementType: PickAll

PickFixed placement type:

draft update --addon kubefleet-clusterresourceplacement \
  --variable CRP_NAME=fmad-demo-crp \
  --variable RESOURCE_SELECTOR_NAME=fmad-demo \
  --variable PLACEMENT_TYPE=PickFixed \
  --variable CLUSTER_NAME_1=cluster-name-01 \
  --variable CLUSTER_NAME_2=cluster-name-02 \
  --variable PARTOF=my-project

Generates the exact YAML from the second sample in the issue with cluster names array.

Bug Fixes

Fixed draft update --addon Parameter

• The --addon parameter was previously ignored, always defaulting to app-routing-ingress
• Now properly uses the specified addon template while maintaining backward compatibility
• When no --addon is specified, still defaults to app-routing-ingress for existing workflows

Fixed ActiveWhen Constraint Handling

• Fixed prompts system to check activeWhen constraints before checking for disabled prompts
• Resolves issue where conditional variables (like cluster names for PickFixed) were incorrectly required in non-interactive mode
• Variables that are inactive due to activeWhen constraints are now properly skipped

Testing

• Comprehensive test suite with fixtures for both PickAll and PickFixed scenarios
• Template validation passes all existing checks
• Backward compatibility verified for existing app-routing-ingress addon
• All existing tests continue to pass

Documentation

Added comprehensive documentation at docs/kubefleet-clusterresourceplacement.md with:

• Usage examples for both placement types
• Variable reference table
• Interactive and non-interactive mode instructions
• Integration guidance for CI/CD pipelines

Fixes #1.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[sjwaight]

@copilot instead of two variables CLUSTER_NAME_1 and CLUSTER_NAME_2 I'd prefer one variable where I can provide a list of cluster names that are then rendered as a YAML list in the output PickFixed manifest. Can you also provide a sample YAML in the documentation for PickFixed showing three clusters.

[Copilot]

@copilot instead of two variables CLUSTER_NAME_1 and CLUSTER_NAME_2 I'd prefer one variable where I can provide a list of cluster names that are then rendered as a YAML list in the output PickFixed ma...

I've updated the implementation to use a single CLUSTER_NAMES variable that accepts a comma-separated list of cluster names instead of two separate variables. The template now supports any number of clusters, and I've added the requested three-cluster example to the documentation. The changes are in commit 82b02b7.

[sjwaight]

I want to use a new verb 'distribute' instead of re-using the 'update' verb.

[Copilot]

I want to use a new verb 'distribute' instead of re-using the 'update' verb.

I've implemented a new draft distribute command specifically for Kubefleet ClusterResourcePlacement functionality. The command defaults to the kubefleet-clusterresourceplacement addon and validates that only kubefleet addons are used. Updated all documentation examples to use the new syntax. Changes are in commit dd91762.

[sjwaight]

Create an example for clusterresourceplacement go and test file in the example folder.

[Copilot]

Create an example for clusterresourceplacement go and test file in the example folder.

I've created the example files for ClusterResourcePlacement in the example folder:

• clusterresourceplacement.go - Shows how to use the kubefleet-clusterresourceplacement template with the handlers.GetTemplate API
• clusterresourceplacement_test.go - Test coverage for the example function

The example demonstrates the PickFixed placement type with three clusters using the CLUSTER_NAMES variable. Both files follow the existing example patterns and all tests pass. Changes are in commit dd5d2e4.

[sjwaight]

Update the main readme.md file to include the new distribute command. Update the linked contoso-air application to use this URL: https://github.com/Azure-Samples/contoso-air

[Copilot]

Update the main readme.md file to include the new distribute command. Update the linked contoso-air application to use this URL: https://github.com/Azure-Samples/contoso-air

I've updated the main README.md file to include the new draft distribute command in both the Commands section and added a dedicated section with usage examples. I've also updated the Contoso Air repository URL from microsoft/ContosoAir to Azure-Samples/contoso-air as requested. The changes are in commit 9e45982.