Hi everyone, I try to deploy a flow in different environments we have to test, validate, and use in production. We have 3 branches: test, staging and prod. I would like to have a logical naming for these flows deployed on AWS. Using the following deployment synthx : python $FLOW_FILE --branch $VERSION --environment=pypi step-functions create I always get the test branch, for example feasibility.test.v1_1_1.FeasibilityFlow. In parallel, for prod, I use the syntax : python $FLOW_FILE --branch $VERSION --production --environment=pypi step-functions create If I want to differentiate between test and staging, it's not really possible. What are your experiences of good environment management? How could I have a nice way of deploying and have the same naming structure for every environment ? (I also considered to use METAFLOW_USER, but it adds "user" in the name, and I cannot use the VERSION value.) Thanks a lot !

sorry for the delay - what nomenclature are you thinking of getting to? you can always set a custom prefix to the state machine that is generated using

METAFLOW_SFN_STATE_MACHINE_PREFIX=foo python flow.py step-functions create

Oh thank you so much ! It could slove our problem ! I would like to get the simplest nomenclature with something like carbon_quantification.test.v1_1_0.CarbonQuantificationFlow, and replace test by whichever environment

perfect!