What problem does it solve?
Direct controllers in Config Connector cannot serve the config-connector export command until they implement AdapterForURL and a correct Export method, and mistakes in unstructured object construction or project binding silently break exported manifests.
Core Features & Use Cases
- AdapterForURL Implementation: Parse CAI URLs into resource identities using
gcpurls.Template/FromExternal and return a populated adapter.
- Export Method Guidance: Correctly order
u.Object assignment before SetName/SetGroupVersionKind, handle reference-bound spec.projectRef versus the project-id annotation, and set identity fields like resourceID and location manually.
- E2E Test Integration: Register the GVK in
tests/e2e/export.go, remove ratcheting exclusions, and generate golden _exported.yaml files aligned with the legacy exporter to avoid _exported_object.diff files.
- Use Case: When adding export support for a resource like
ArtifactRegistryRepository, follow the workflow to implement the adapter, wire up the test harness, and produce verified golden export output.
Quick Start
Ask the agent to add export support for a specific Config Connector direct controller resource and verify it with the unified E2E test runner.