Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hello - I was wondering if there is a way to prevent DockerStorage from being built / pushed when the Flow is already registered with a known idempotency_key. Ideally, the storage should only be built/pushed when the Flow has changed.

Hey <@U01AQF76WT1>, what version are you on and how are you registering? CLI or `flow.register()`?

I am on 14.22 and I am registering using `flow.register(..., idempotency_key=flow.serialized_hash())`

~How long are your builds taking? It should be pretty fast because we made a change that respected the Docker cache.~  I guess the upload may take a while.

The issue is not a question of speed / upload time. I want to freeze the image used at registration, and only update it when the flow changes.

The image will still build even with the idempotency key. So if the Flow is the only reason causing the builds, the suggestion is to use another form of Storage like S3 or Github, and then pair that with `DockerRun`. `DockerRun` can pull the image to run on, and then the Flow will be retrieved from Storage and run on top of that image.