https://prefect.io logo
#prefect-community
Title
# prefect-community
j

Joshua Greenhalgh

04/01/2022, 4:00 PM
Hi wonder if someone could help me - I am trying to implement a combination of module storage with kubernetes job run config - my process is to build a python module with all my flows within a docker image - push this image to a registry and then specify this image as the one that the kubernetes job runs - now when I register these flows with cloud if the code in the module changes I would expect to see a version bump however I just get the following message on subsequent registrations;
Copy code
Collecting flows...
Processing 'flows':
  Building `Module` storage...
  Building 'first_flow'... Done
Writing output to 'flows.json'
========================== 1 built ==========================
Collecting flows...
Processing 'flows.json':
  Registering 'first_flow'... Skipped (metadata unchanged)
================== 0 registered, 1 skipped ==================
I am running the following commands foe the above;
Copy code
> prefect build -m 'flows'
> prefect register -j ./flows.json --project test
k

Kevin Kho

04/01/2022, 4:02 PM
You can use the
--force
flag when you register to force it. If the metadata doesn’t change (DAG structure), Prefect won’t register by default when using the CLI
j

Joshua Greenhalgh

04/01/2022, 4:02 PM
I am probably quite light on details here so can try to fill any missing ones in if needed - basically want to know how do I get the register step, when using module storage, to bump the version when code changes?
Thanks @Kevin Kho - so there is no attention paid to like hashes of the module contents or anything like that?
--force
is probably what I want to do anyway!
k

Kevin Kho

04/01/2022, 4:04 PM
The hash is on the DAG and metadata like RunConfig and stuff but within a task we don’t see changes
j

Joshua Greenhalgh

04/01/2022, 4:04 PM
Ok cool!
2 Views