Tilak Maddy
12/06/2021, 10:54 AMUserWarning: A flow with the same name is already contained in storage; if you changed your Flow since the last build, you might experience unexpected issues and should re-create your storage object.
serialized_flow = flow.serialize(build=build) # type: Any
Flow URL: <https://cloud.prefect.io/XXX/flow/ZZZ>
└── ID: XXXX
└── Project: test_proj_2
└── Labels: ['dev']
Hey y'all I am running flows in multiple projects but all the flows have the same name and same storage (by design, i don't wish to change the name). However when I register the flow to several projects I get this warning every time I call flow.register(project_name)
(with different metadata of course like schedule time, etc) on a different project. I want to know what that warning means . Since I have the flows setup in production I want to know that if I update the flow metadata for one project is it going to do the other flows dirty ?Anna Geller
all the flows have the same nameThis is not allowed, flow name must be unique across a project
Tilak Maddy
12/06/2021, 10:56 AMAnna Geller
Tilak Maddy
12/06/2021, 10:57 AMTilak Maddy
12/06/2021, 10:57 AMAnna Geller
Tilak Maddy
12/06/2021, 10:58 AMTilak Maddy
12/06/2021, 10:59 AMAnna Geller
Anna Geller
Anna Geller
Tilak Maddy
12/06/2021, 11:47 AMIs it just parameter values and schedules that differ across projects?Yes you are spot on ! I will surely explain more, I had gone away for a while ... in a meeting.
Tilak Maddy
12/06/2021, 11:55 AMflow.register(pipeline_id)
to all other projects when I make the change
Regarding my deployment scenario it is what we have discussed here in this thread https://prefect-community.slack.com/archives/CL09KU1K7/p1638614318370800?thread_ts=1638446024.174500&cid=CL09KU1K7 (Basically a GCP vertex with github storage)Anna Geller
Tilak Maddy
12/06/2021, 12:13 PMAnna Geller
Tilak Maddy
12/06/2021, 12:24 PMAnna Geller
Anna Geller