Hi, I have a quick question regarding fast registr...
# ask-the-community
s
Hi, I have a quick question regarding fast registration via flytectl. According to docs, there is no difference between regular and fast registration - so does that mean that if there are no python dependency changes and I want to use fast registration, then I can add
--fast
flag to my
pyflyte package ...
command, but leave the
flytectl register files …
command the same and then forego the docker build process?
b
That’s correct 👍 I think you might also need to use
pyflyte ... serialize fast
beforehand 🙂 Under the hood, this will create a zip file with all your modules code which is then uploaded to your blob storage together with the workflow and task definitions
s
Hi @Bernhard Stadlbauer thanks! But I’m not sure what you mean by
pyflyte serialize
? I’ve always only done
pyflyte package
to output
flyte-packages.tgz
and then
flytectl register files --archive flyte-packages.tgz
- do I need to run another command besides these?
b
I think in the case of
pyflyte package
you’ll need the
--fast
flag to get to the same result
s
OK so no need for
pyflyte serialize
?
b
Yep 👍 If I’m not mistaken
pyflyte package
is the newer version that replaces
pyflyte serialize
Looking at the docs, I believe you should also be able to use
pyflyte register
instead of
pyflyte package
and
flytectl register
in case you prefer that. Got that from
pyflyte register --help
s
Sorry I missed this - I think there’s a difference there (based on the docs anyway). Not sure exactly, but if used in a team, I think flytectl is preferred?
Thanks for clarifying this by the way