Diego Marquez

Hi @clecompte-apple, thanks for reporting this! Do you happen to have a sample setup that reproduces the issue? cc @mpeddada1 @ldetmer Are there tests for builds with authenticated endpoints?

cc: @jaycee-li @sasha-gitg

Hi @leungwh, thanks for reporting this issue. This situation is similar to [https://github.com/GoogleContainerTools/jib/issues/4382](url) (but may not count as duplicate). Would you mind sharing more details about your project structure (even...

/gcbrun

@blakeli0 I removed `gapic_generator_version` altogether. We now only rely on `DOCKER_GAPIC_GENERATOR_LOCATION` that will point to the jar we need and not care about the location. This however brought many changes...

@JoeWang1127 @blakeli0 the integration tests now can't be locked to a specific generator version, so we will constantly need to update them. A few ideas: * Add an `--update` flag...

[spring downstream check failing](https://github.com/googleapis/sdk-platform-java/actions/runs/10625302690/job/29455529366) because the release job still doesn't publish the maven artifacts https://github.com/GoogleCloudPlatform/spring-cloud-gcp/pull/3138#issuecomment-2318598130  cc: @mpeddada1

From discussion with @blakeli0 and @JoeWang1127, we can lock in a specific version string of the generator, download it in our integration test and then override the well-known location via...

@JoeWang1127 I modified the integration test to lock-in a specific generator jar downloaded via `mvn`. PTAL when you have a chance :)

@scrat98 did the documentation @mpeddada1 shared cover your use case? Looks like this could be a more specific situation we can cover in the docs. If you found a solution,...