Add Missing Field

To add a missing GCP field to a KCC direct controller, you update Go types, register fuzzer expectations, and modify proto-to-KRM mappers. This ensures the new attribute successfully round-trips through reconciliation and passes apichecks.

KCC fuzzer tests fail when a GCP API field is missing because the proto-to-KRM mappings and expected spec fields are misaligned. You must remove the field from unimplemented lists and update mappers to make apichecks and generation logic reflect reality.

Updating KCC proto mappings requires symmetric updates to both _FromProto and _ToProto functions, including manual parent mappers for nested types. This correct round-tripping allows the controller to properly reconcile the newly added attribute.

To regenerate golden tests after adding a field to a Config Connector resource, you run the generators, update golden compare output, and use WRITE_GOLDEN_OUTPUT. You also need to adjust resource fixture testdata and patch mockgcp stubs for observed outputs.

You must update both Spec and ObservedState structs symmetrically when adding a missing field to KCC direct controllers. This involves modifying the appropriate _types.go file with correct naming and KCC reference usage for URI fragments to ensure proper reconciliation.

You should patch mockgcp when adding a missing field to KCC if the new attribute includes observed outputs. Providing reasonable mock behavior for the new output field ensures your unit and golden tests validate the updated reconciliation logic correctly.