Hi Flyte community. Is there a way to create launch plans outside a Py binary (using Flytectl)? From the documentation, it seems that you can use flytectl to activate/deactivate launch plans but you cannot define new launch plans as the API for defining a new launch plan requires a reference to the workflow Py function. We are interested in a set up where you define your task and workflows in Python by detach that from setting up launch plans. For example, have an automated system parse a YAML file that describes the desired launch plans and then uses flytectl to create LPs without the need to have depend on the Py code of the workflow. Is that possible?

Or a user experience similar to Flyte operator that reconciles LaunchPlan custom resources

The API to create launchplans is here: https://docs.flyte.org/en/latest/api/flyteidl/docs/admin/admin.html#launchplancreaterequest It only requires a reference to the workflow and an identifier... You can also create

from flytekit.models import launch_plan

lp = launch_plan.Launchplan(id=, spec=, closure=)
remote = FlyteRemote....
remote.raw_register(lp...)

There isn't, at the moment, plans to create a reconciler operator for LPs... though that's not a bad idea (if you are interested, @clean-glass-36808 😉 )

That is the plan. We certainly want a git ops workflow for (de)activating launch plans but were a little confused around whether we could do that for creating launch plans too given the python side ux.