pjfanning opened a new pull request, #1900:
URL: https://github.com/apache/pekko-connectors/pull/1900

   ### Motivation
   The `gcloud-pubsub-emulator_prep` docker-compose service uses 
`martynas/gcloud-pubsub-client`, an unpinned third-party image last updated in 
2018, just to create the two topics and two subscriptions the 
`google-cloud-pub-sub` and `google-cloud-pub-sub-grpc` integration tests expect.
   
   ### Modification
   Replace it with the Pub/Sub emulator's own REST API: the prep service now 
runs the same `google/cloud-sdk` image as the emulator (so no additional image 
is pulled at all), waits for the emulator to answer, then issues four `curl` 
PUTs to create `simpleTopic`/`simpleSubscription` and 
`testTopic`/`testSubscription`. The `gcloud` CLI cannot target the emulator for 
resource creation, which is why the REST API is used.
   
   Note: #1886 bumps the sibling emulator service's `google/cloud-sdk` tag to 
583.0.0; this PR uses the tag currently on main (554.0.0) for the prep service, 
and whichever PR lands second should align the two tags (a one-line follow-up).
   
   ### Result
   The Pub/Sub emulator tests no longer depend on an abandoned third-party 
image; the prep logic is visible in the compose file.
   
   ### Tests
   - `docker compose config` validates.
   - The `connectors (google-cloud-pub-sub)` and `connectors 
(google-cloud-pub-sub-grpc)` CI jobs start this service (`docker compose up -d 
gcloud-pubsub-emulator_prep`) and their suites depend on the 
topics/subscriptions it creates.
   
   ### References
   None - test docker image maintenance


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to