-
Notifications
You must be signed in to change notification settings - Fork 670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] FlyteKit- Allow users to avoid generating default launchplans #462
Labels
enhancement
New feature or request
untriaged
This issues has not yet been looked at by the Maintainers
Milestone
Comments
EngHabu
added
enhancement
New feature or request
untriaged
This issues has not yet been looked at by the Maintainers
labels
Aug 7, 2020
CC @thechopkins |
8 tasks
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 6, 2022
…#462) * updated flyteplugins version Signed-off-by: Daniel Rammer <[email protected]> * bumping flyteplugins version Signed-off-by: Daniel Rammer <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 6, 2022
* Bump flyteidl version Signed-off-by: Kevin Su <[email protected]> * Bump flyteidl version Signed-off-by: Kevin Su <[email protected]> * lint Signed-off-by: Kevin Su <[email protected]> * make ReadHeaderTimeout configurable Signed-off-by: Kevin Su <[email protected]> * update_boilerplate Signed-off-by: Kevin Su <[email protected]> * Address comment Signed-off-by: Kevin Su <[email protected]> * Address comment Signed-off-by: Kevin Su <[email protected]> * fix test Signed-off-by: Kevin Su <[email protected]> * update run-tests Signed-off-by: Kevin Su <[email protected]> Signed-off-by: Kevin Su <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
Signed-off-by: Yuvraj <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
* ci: resolve docker build issues * chore: remove unneeded changes Signed-off-by: Nastya Rusina <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Aug 9, 2023
…#462) * updated flyteplugins version Signed-off-by: Daniel Rammer <[email protected]> * bumping flyteplugins version Signed-off-by: Daniel Rammer <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Aug 21, 2023
* Bump flyteidl version Signed-off-by: Kevin Su <[email protected]> * Bump flyteidl version Signed-off-by: Kevin Su <[email protected]> * lint Signed-off-by: Kevin Su <[email protected]> * make ReadHeaderTimeout configurable Signed-off-by: Kevin Su <[email protected]> * update_boilerplate Signed-off-by: Kevin Su <[email protected]> * Address comment Signed-off-by: Kevin Su <[email protected]> * Address comment Signed-off-by: Kevin Su <[email protected]> * fix test Signed-off-by: Kevin Su <[email protected]> * update run-tests Signed-off-by: Kevin Su <[email protected]> Signed-off-by: Kevin Su <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
untriaged
This issues has not yet been looked at by the Maintainers
Motivation: Why do you think this is important?
Launchplans allow authors to choose how users ultimately invoke a workflow. This includes requiring certain inputs to be filled or forcing certain values to certain inputs. There might be cases where the default launchplans that FlyteKit automatically generates are undesirable to be exposed.
Goal: What should the final outcome look like, ideally?
@workflow_class(disable_default_launch_plan=True)
would not generate the default launchplan.Flyte component
The text was updated successfully, but these errors were encountered: