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;

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 ==================

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

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?

The hash is on the DAG and metadata like RunConfig and stuff but within a task we don’t see changes

Ok cool!