Skip to content

Commit

Permalink
Remove the referral to a flowchart (flyteorg#488)
Browse files Browse the repository at this point in the history
Remove the following statement about when to write a backend plugin: 
"To understand when you should write a backend plugin refer to - TODO: Flow chart that helps you decide when to write a backend / flytekit plugin?"
  • Loading branch information
SandraGH5 authored Nov 19, 2021
1 parent e452bad commit 4fc3229
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions cookbook/core/extend_flyte/custom_task_plugin.py
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,7 @@
Flytekit is designed to be extremely extensible. You can add new task-types that are useful only for your use-cases.
Flyte does come with the capability of extending the backend, but that is only required if you want the capability to be
extended to all users of Flyte, or there is a cost/visibility benefit of doing so. To understand when you should write
a backend plugin refer to - TODO: Flow chart that helps you decide when to write a backend / flytekit plugin?
extended to all users of Flyte, or there is a cost/visibility benefit of doing so.
The following demo shows how to build Flyte container task extensions, with an SQLAlchemy extension as an example:
Expand Down

0 comments on commit 4fc3229

Please sign in to comment.