Hi all! Hoping to start a conversation about namin...
# ask-community
j
Hi all! Hoping to start a conversation about naming flows vs. naming deployments. Does anyone have a standard they employ to associate flows -> deployments? Or simply a datetime standard to create unique flow names? Looking to decide if I should focus on getting a custom "flow naming scheme" when I am mainly focused on running deployments.
j
I just simplified on using the same name for both… not sure I’m happy with my decision, but makes it “easy” to
run_deployments
using the name of the flow and deployment like so…
Copy code
run_deployment(
        name="logs-for-date-range/logs_for_date_range",
        parameters={"org_id": <http://org.pk|org.pk>, "start": start_date, "end": end_date},
        timeout=0,
    )
Interestingly at the moment that particular line is not working for me because it is not using my environment set
PRFECT_API_URL
variable.
Again, I’m not sold on my naming choice, but it works and when I’m writing admin functions to be able to initialize a deployment through our application interface… I have the flows inline with the application code. So even the above names come from the name of the function that is the entry point flow.
👍 1
j
Thanks for your input and thoughts! I'll definitely keep it in mind