Joe Hartshorn09/25/2023, 8:33 AM
the tasks into it, I won’t know the version of the image to refer to in the task decorators. It’s a little bit circular, isn’t it? Using
tag wont work in my org because in prod we always used pinned container versions. Plus it seems like that might make it harder to reproduce older runs once the latest tag moves. I must be missing something, how have you worked around this?
Bernhard Stadlbauer09/25/2023, 8:58 AM
. For commits on main we’re using `main-<short-commit-hash>. For released (tagged) versions we’re usually using the version number. 2. Build and tag and push docker image based on the version from step (1) 3. Serialize and register the Flyte workflows based on the version from (1) and the docker image from (2). This step is dependent on the success of step (2). Depending on whether it’s a feature branch, etc. we’re adjusting the domain to register to accordingly
Joe Hartshorn09/25/2023, 9:04 AM
Bernhard Stadlbauer09/25/2023, 9:18 AM
option whilst serializing/registering (depends on what command you use?). This would then be the default image used for all your tasks. In case you need the image in the
decorator (e.g. in the case of different images in a workflow) - you can follow this doc
Joe Hartshorn09/25/2023, 9:20 AM
Image reference is specified, but the version is derived from the default images versionThank you for the quick responses! This is exaactly what I was looking for!