Add New MockGCP Resource

You create a mock GCP service by implementing service.go and resource CRUD controllers under mockgcp, registering proper clients, and validating against recorded fixtures. This enables reliable local testing without hitting real endpoints.

Mocking Long-Running Operations involves implementing optional LRO routes within your mock service.go file using grpc-gateway patterns. You register the proper operation routes alongside standard resource CRUD handlers to support asynchronous API behaviors.

Cross-service log corruption occurs when normalization is not properly scoped. You must implement normalize.go with Previsit scoped specifically to the service host so test fixtures remain consistent and avoid cross-service log corruption.

The best way to validate a new mock GCP resource is capturing real GCP fixtures using record-gcp, then iteratively comparing mock behavior with compare-mock until discrepancies are resolved and expectations match.

Yes, adding new mocked endpoints backed by published proto definitions is required. You identify the target service and protos first, adding generation paths when necessary before creating the mock service and controller code.

Mockgcp is a framework for extending mock GCP behavior so tests and development can exercise new GCP APIs locally. You need it when teams require reliable local testing without hitting real endpoints while keeping logs stable.