Summary
The user is asking if it's possible to create launch plans using Flytectl without needing a Python binary. They mention that while the documentation states Flytectl can activate or deactivate launch plans, it does not support defining new launch plans without a workflow Python function. The user seeks a method to define tasks and workflows in Python while allowing for independent creation of launch plans, possibly through an automated system that uses a YAML file. They reference the API for creating launch plans, which requires a workflow reference and an identifier, and provide a code snippet for creating a launch plan using Flytekit. The user notes that there are currently no plans for a reconciler operator for launch plans but considers it a good idea.
sovietaced
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 workflows too given the python side ux.
habuelfutuh
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
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, <@U072ZEKG7V0> :wink: )
sovietaced
Ie. A Flyte operator that reconciles LaunchPlan custom resources
hossein
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?