mirror of
https://github.com/langchain-ai/langgraph.git
synced 2026-10-18 14:07:31 +02:00
gdibben
c58d24c11f
--push-to always builds (or retags a local --image) and pushes, even when the image already exists at the destination. That breaks CI/CD pipelines where the build/push step and the deploy step run in separate jobs: the deploy job has no local copy of the image to retag, and --image requires one (it runs `docker image inspect`). --image-uri takes a full image reference already in a registry (tag or digest) and deploys it directly via source_revision_config.image_uri, with no local Docker involvement at all: no inspect, no build, no tag, no push. Same placement (--listener-id/--k8s-namespace, or auto-select the sole listener) and update-in-place semantics as --push-to, since both produce an external_docker deployment. Refactors CustomerRegistrySource's image-acquisition step into two variants (BuildAndPush for the existing --push-to/--image flow, PublishedImage for the new flag) so --create/--update/placement logic stays shared and unchanged.