kcc-direct-identity-implementer

Implement IdentityV2 and ExternalIdentifier logic for direct KCC resources using gcpurls.Template.

1.1k|367|Updated Apr 8, 2019
One-click install
npx skills add https://github.com/GoogleCloudPlatform/k8s-config-connector --skill kcc-direct-identity-implementer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kcc-direct-identity-implementer
Source: https://github.com/GoogleCloudPlatform/k8s-config-connector/tree/main/.gemini/skills/kcc-direct-identity-implementer
Command: npx skills add https://github.com/GoogleCloudPlatform/k8s-config-connector --skill kcc-direct-identity-implementer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you implement canonical IdentityV2 and ExternalIdentifier behavior for direct Config Connector (KCC) resources so the resource’s GCP URL mapping is correct, stable, and matches the expected gcpurls.Template pattern.

Core Features & Use Cases

  • IdentityV2 implementation for direct KCC resources: Creates the required identity file and wires it to the resource’s canonical identity model.
  • Canonical GCP URL template parsing: Ensures GCP URL parsing and formatting follow the gcpurls.Template approach for reliable ExternalIdentifier behavior.
  • Parent & hierarchy support: Handles resources that can exist in multiple hierarchy patterns (for example global vs regional) by using fields like Spec location presence to choose the right mapping and conversion logic.
  • Journaling of template mapping complexities: Records multi-parent or multi-hierarchy mapping nuances into the appropriate journal file to preserve implementation knowledge.

Quick Start

Implement the IdentityV2 and ExternalIdentifier interfaces for your direct KCC resource by creating the apis/<service>/<api_version>/<resource_lower>_identity.go file using gcpurls.Template with your resource’s GCP URL template and API version.

Frequently Asked Questions about kcc-direct-identity-implementer

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

FAQPage Schema
How do I implement IdentityV2 for direct Config Connector resources?

Implement IdentityV2 for direct Config Connector resources by creating the apis/<service>/<api_version>/<resource_lower>_identity.go file and wiring the canonical identity model using gcpurls.Template parsing to ensure stable GCP URL mappings.

What is ExternalIdentifier logic in Kubernetes Config Connector?

ExternalIdentifier logic in Kubernetes Config Connector defines how a resource maps to its canonical GCP URL. It uses gcpurls.Template-based parsing and formatting to produce reliable external identifier behavior for direct KCC resources.

How do I handle multi-hierarchy GCP URL mappings in KCC resource generation?

Handle multi-hierarchy GCP URL mappings in KCC by branching ExternalIdentifier conversion logic keyed off the Spec location field, allowing the resource to correctly switch between global and regional hierarchy patterns.

How do I wire Spec ProjectRef and Location for direct KCC resources?

Wire Spec ProjectRef and Location for direct KCC resources within the identity implementation file. ProjectRef is always required, while Location is applicable conditionally and used to determine the correct gcpurls.Template formatting branch.

Why does my KCC resource GCP URL mapping fail for regional and global resources?

KCC resource GCP URL mapping fails when String and FromExternal branching does not correctly key off the Spec location field. You must implement separate gcpurls.Template parsing logic to handle both regional and global hierarchy cases.

Where do I journal multi-parent template mapping nuances for Config Connector resources?

Journal multi-parent template mapping nuances for Config Connector resources into the appropriate journal file during identity implementation. This preserves complex hierarchy mapping knowledge for direct KCC resource generation.