feat(provider): GCE provider (experimental, mock-validated)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 30
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Add a GCE provider over cloud.google.com/go/compute with a new stateful gcpfake replicating the awsfake requirements: poll-compatible state transitions, exact error codes/strings the retry paths match, non-nil fields the code dereferences, single-page pagination, permissive catalogs + Seed* overrides, FailNext error injection, call/input recorder, mutex, ResourceCounts/Empty leak assertions.
No GCP credentials exist in CI, so the provider ships experimental — mock-validated orchestration only. A fake built from docs alone is unanchored; policy: mock-green/real-red is a fake bug, not a flake. real-gcp label family lands credential-gated (skipped) until secrets exist.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the existing awsfake requirements with the cloud.google.com/go/compute provider surface; no specific files or tests are named. Validate the provider through mock-based orchestration, including state transitions, retry-matched errors, pagination, failure injection, recording, and leak assertions. Done means mock validation passes without requiring GCP credentials, while real-GCP tests remain credential-gated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100