I have a pipeline where in step 1, I build and deploy a docker container image to a private Google Cloud registry, updating the `:latest` tag. Then in step 2, I use a service based on the `:latest` tag for that very same image.
Does Pipelines guarantee that a custom service image tag will be pulled and instantiated for a step only after previous steps have completed?
Depending on the design of Pipelines, it's plausible that it could pull and run all services in parallel when a pipeline executes instead of accounting for the possibility that a step could alter a service for a later step. I'm not sure the documentation is clear on this particular point.
Haven't tested this for myself yet, but hopefully the question is interesting to others.