kcc-identity-reference

To implement IdentityV2 for Config Connector resources, you generate or update the resource's `_identity.go` file to conform to the canonical `gcpurls.Template` pattern. This ensures proper identity normalization and downstream resolution across multiple API groups and versions.

KCC reference parsing breaks for unstructured inputs when `getIdentityFrom<Kind>Spec` cannot handle `*unstructured.Unstructured` objects during Normalize. You must update the implementation to safely process both typed objects and unstructured inputs without causing panics.

You map GCP URL template variables to KCC struct fields by deriving the exact URL segments from `cloudassetinventory_names.jsonl` or existing implementations. This enforces struct-field and template-variable alignment to prevent underscore mismatches during identity resolution.

The best way to generate KCC reference boilerplate is to update the resource's `_reference.go` file to implement `refs.Ref`, including GVK registration and external parsing. This maintains canonical reference parsing and prevents code from drifting away from the `gcpurls.Template` pattern.

Yes, KCC identity normalization requires validating compilation via `go vet` and `go build` after updating the identity and reference files. This validation ensures the generated IdentityV2 and refs.Ref implementations compile correctly without structural errors.