I’m wondering if it is possible to change which bl...
# ask-communityc
Choenden Kyirong
10/18/2023, 6:11 PMI’m wondering if it is possible to change which block to use within a task depending on the deployment version of a flow or is this a badly designed approach? For example, i have a flow that can either run 2 different types of infra (decided via deployments) but the db connection values will need to change depending on what infra it is using.
k
Kevin Grismore
10/18/2023, 6:12 PMif you're `.load()`ing the block in your task, and there's two different deployments of that flow, you could have a param to the flow that selects the appropriate block name that differs per deployment
Kevin Grismore
10/18/2023, 6:14 PMwhat's the different infra? maybe there's a more concise way to do it if the infra can be inferred from the execution environment
c
Choenden Kyirong
10/18/2023, 6:16 PMahh okay gotcha. yeah, this is the approach i had in mind as well but was thinking there might be a better approach. For example, somehow through the actual
prefect.yamlChoenden Kyirong
10/18/2023, 6:20 PMThe reason for the difference in db details for this example is that the cloud run job is connected to a vpc connector which needs to use the internal IP of the db (also on gcp, sql instance). Whereas, the VM (in a separate project unfortunately), is using the public IP (whitelisted as a connection). The potential gcp workaround would be to do some sort of shared vpc approach i think @Kevin Grismore
k
Kevin Grismore
10/18/2023, 6:34 PMgotcha, if they're in the same project there's probably not an easy way to tell the difference at runtime
Kevin Grismore
10/18/2023, 6:35 PMI've been looking into flow run context to see if there's any way to grab something like a deployment's tags or work pool to differentiate it but I haven't found anything yet
c
Choenden Kyirong
10/18/2023, 6:39 PM@Kevin Grismore it seems like
runtime.deployment.namek
Kevin Grismore
10/18/2023, 6:40 PMahaaaa
Kevin Grismore
10/18/2023, 6:40 PMthat seems useful
🙌 1
Kevin Grismore
10/18/2023, 6:47 PMmy advice here is that, while something like this will work, having something more explicit like a flow param still may be the best option. deployment names are easy to change, and you don't want to forget they have some kind of code dependency that breaks, so if you do use it, make sure you've got good error handling around it
c
Choenden Kyirong
10/18/2023, 6:53 PMthats a great point. I’ll definitely keep this in mind. The explicitly of the flow param is quite clear- the deployment name dependancy could easily be forgotten.