https://flyte.org
Join Slack
Hello! I am working through setting up a CI / CD process to register and activate launch plans. I am...
# flyte-support
a
Hello! I am working through setting up a CI / CD process to register and activate launch plans. I am new to CI / CD, so I am curious if folks here have a good solution. I like how 
pyflyte
can register a file or folder of launch plans, but I am not exactly sure how to active them all. I don’t want to have to active specific launch plans inside the github actions workflow. My best idea is to throw everything in a Makefile. Any advice is much appreciated!
Copy code
# only sudo code implemented
.SILENT: deploy
.PHONY: deploy
deploy
	pyflyte register [flags] ./recsys/deploy/launchplans.py;
    # I could list them here?
	flytectl update [flags] launchplan prod_ease_train;
@thankful-minister-83577 for visibility
t
btw for reference, these are some of the calls you can do. https://docs.flyte.org/projects/flytectl/en/latest/gen/flytectl_get_launchplan.html#id1
yeah nm - confirmed internally.
the activate-all command is a legacy lyft feature that never got ported.
let’s make an issue for this - handling around this should have good ergonomics. requiring users to call these endpoints and loop over things in a script is not good.
i’ll put together the issue.
🙌 1
cc @high-park-82026 can you skim that issue?
make sure it makes sense
h
Added some comments here: https://github.com/flyteorg/flyte/issues/3109 Maybe @abundant-hamburger-66584 can chime in too. that would be great
155 Views
Open in Slack
PreviousNext
Powered by

Flyte

Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Powered by