does anyone have good patterns for registering flows via ci/cd? ideally id like to register only the flows that changed automatically on a git push, and be able to use different run configs for each, while also handling env vars that may be different in prod/dev. currently i have a script that loops through all my files in my flows directory and registers all flows using extract_flow_from_file. it runs on a push but the way i have it set up it: • always registers all flows, regardless of whether they have changed or not • has to pass the same env values to all flows, regardless of what the flow actually needs • passes the same run config to all flows, not allowing me to customize memory requests per flow any guidance on what to do here?

Have you seen this discussion yet?

yes. altho i think i missed this line which would solve the latter two of my issues:

A custom Kubernetes job template, which includes labels/annotations for logging and monitoring

do you know how id do that? i dont see code for it

I think this is a good example and he also shows how to attach it to the Flow RunConfig. Does that help you?