Skip to content
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

Add new community provider: Flyte #22646

Closed
wants to merge 5 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
add additional parameters to docs
Signed-off-by: Samhita Alla <aallasamhita@gmail.com>
samhita-alla committed Mar 31, 2022
commit 59f6ae22717aed82dbae46f21671a697908dbe09
3 changes: 2 additions & 1 deletion docs/apache-airflow-providers-flyte/operators/flyte.rst
Original file line number Diff line number Diff line change
@@ -30,7 +30,8 @@ The AirflowFlyteOperator requires a ``flyte_conn_id`` to fetch all the connectio
parameters that may be useful to instantiate ``FlyteRemote``. Also, you must give a
``launchplan_name`` — to trigger a workflow, or ``task_name`` — to trigger a task; you can give a
handful of other values that are optional, such as ``project``, ``domain``, ``max_parallelism``,
``raw_data_prefix``, ``assumable_iam_role``, ``kubernetes_service_account``, ``version``, ``inputs``, ``timeout``, and ``poll_interval``.
``raw_data_prefix``, ``assumable_iam_role``, ``kubernetes_service_account``, ``labels``, ``annotations``,
``version``, ``inputs``, ``timeout``, and ``poll_interval``.

The executions will be triggered synchronously by default on Flyte. You can set the ``asynchronous`` parameter to
``True`` to trigger the executions asynchronously.