Fix unavailable Google Cloud emulator image tags in tests - #12065
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 8 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthroughThe Google Cloud emulator tests update their Docker image tags to ChangesGoogle Cloud emulator test image updates
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to Google Cloud emulator tests now use the available 583.0.0-emulators image tag, replacing unavailable tags that prevented test containers from starting. No merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
55a5ce6 to
1ef4930
Compare
Replace unavailable emulator tags with 583.0.0-emulators to restore gcloud CI.
1ef4930 to
8dc4c7c
Compare
The gcloud tests fail before container startup because
gcr.io/google.com/cloudsdktool/google-cloud-cli:441.0.0-emulatorsand465.0.0-emulatorsreturn404 manifest unknown. This affects seven tests across Bigtable, Datastore, Firestore, and Pub/Sub, including this CI run.Update the seven image references to the available
583.0.0-emulatorstag so the emulators can be pulled and the tests can run again.Summary by CodeRabbit