<#6460 [Core feature] fast-fail inamgespec> Issue ...
# flyte-github
a
#6460 [Core feature] fast-fail inamgespec Issue created by dansola Motivation: Why do you think this is important? Right now, if
ImageSpec
can't find or create an image (e.g. Docker isn't running), it assumes the image exists with
f"Flytekit assumes the image {img_name} already exists."
. For CI/CD processes, it may not be ideal for an automated system to assume an image exists. Goal: What should the final outcome look like, ideally? Ideally, the
register
or
run
command can take a
--imagespec-fast-fail
flag which will fail the registration or run command if the image can't be built. Describe alternatives you've considered Alternatively,
ImageSpec
could take an argument that prevents registration from succeeding if the image can't be found or built. Propose: Link/Inline OR Additional context Proposition: 1. Add a
--imagespec-fast-fail
flag 2. Add a
imagespec_fast_fail
argument to
ImageConfig
which is included in the
SerializationSettings
during registration. 3. In
ImageBuildEngine.build
, include the
imagespec_fast_fail
arg. 4. In
ImageSpec
, in
should_build
, raise an error if
imagespec_fast_fail==True
and the image can't be found or built. Are you sure this issue hasn't been raised already? • Yes Have you read the Code of Conduct? • Yes flyteorg/flyte