1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by wild-endeavor

<https://github.com/flyteorg/flytekit/commit/71d78988752cf804e3fb05f9d1f6321ca8b2146b|71d78988>

- Improve workflow decorator type hints with overload (#1635) flyteorg/flytekit

Release - v1.6.0 New release published by eapolinario What's Changed • Unify sqlalchemy Dockerfiles by @eapolinario in #1585 • Add classifier for Python 3.11 by @honnix in #1589 • Pyflyte build imageSpec by @pingsutw in #1555 • Feature/3506: Improve Type Conversion errors, use rich to prettify error messages by @cosmicBboy in #1582 • Add support nested FlyteFile in pyflyte run by @pingsutw in #1587 • Set cache_regions=True in the case of s3fs by @eapolinario in #1592 • Set default ComSpec when running on Windows by @pingsutw in #1595 • Feature: add activate-launchplan command to pyflyte by @wckdman in #1588 • Remove extraneous debug statement by @wild-endeavor in #1596 • Add log streaming to papermill plugin by @CalvinLeather in #1129 • Set lower bound for s3fs by @pingsutw in #1598 • Implement horovod task in mpi plugin by @ByronHsu in #1575 • Add ImageRender class for Flyte Decks by @peridotml in #1599 • Bump tensorflow from 2.10.0 to 2.11.1 in /plugins/flytekit-mlflow by @dependabot in #1586 • Handle batchable lists of length 0 by @eapolinario in #1600 • pyflyte run imperative workflow by @pingsutw in #1597 • Backfill should fill in the right input vars by @kumare3 in #1593 • Pyflyte prettified by @kumare3 in #1602 • pyflyte run now supports json/yaml files by @kumare3 in #1606 • Add is_inside func to ImageSpec by @pingsutw in #1601 • Measuring the time taken for each component when executing a task by @Yicheng-Lu-llll in #1581 • Skip the image building process if the check for its existence fails by @pingsutw in #1614 • Enable torch elastic training (torchrun) by @fg91 in #1603 • update sphinx youtube plugin by @pingsutw in #1619 • Read polar dataframe without copying to local by @pingsutw in #1618 • Add default spark image by @pingsutw in #1616 • Lazy load modules by @pingsutw in #1590 • Override node name with a name containing underscore by @pingsutw in #1608 • External Plugin Service (grpc) by @pingsutw in #1524 • Include traceback in errors from admin by @wild-endeavor in #1621 • Add support for copying all the files in source root by @pingsutw in #1622 • Fix PipelineModel transformer issue 3648 by @peridotml in #1623 • update GH workflow for external plugin service by @pingsutw in #1624 • [Issue-3617] Enables FlyteFiles, FlyteDirectors, and StructuredDatasets inputs in papermill plugin by @peridotml in #1612 • Add support for using a list as an input for a subworkflow by @pingsutw in #1605 • Improve task decorator type hints with overload by @ringohoffman in #1631 • add annotation option for serialization by @elibixby in #1615 • delete removed data persistence classes from docs by @cosmicBboy in #1633 • Improve workflow decorator type hints with overload by @ringohoffman in #1635 New Contributors • @wckdman made their first contribution in #1588 • @peridotml made their first contribution in #1599 • @ringohoffman made their first contribution in #1631 • @elibixby made their first contribution in #1615 Full Changelog: v1.5.0...v1.6.0 flyteorg/flytekit

1 new commit pushed to

<https://github.com/flyteorg/flyte/tree/master|master>

by eapolinario

<https://github.com/flyteorg/flyte/commit/88f6d15cd2c0b434600dfcb6ff631d7803abb0c2|88f6d15c>

- Update Flyte components (#3675) flyteorg/flyte

#3677 Update Flyte components Pull request opened by flyte-bot Updated flyte deployment • Updated GCP Flyte kustomize generated manifest file • Updated EKS Flyte kustomize generated manifest file • Updated Sandbox Flyte kustomize generated manifest file • Updated TEST Flyte kustomize generated manifest file • Updated GCP Flyte helm generated manifest file • Updated EKS Flyte helm generated manifest file • Updated Sandbox Flyte helm generated manifest file • Updated TEST Flyte helm generated manifest file • Auto-generated by [flyte-bot] flyteorg/flyte GitHub Actions: build-and-push-single-binary-image GitHub Actions: compile GitHub Actions: trigger-sandbox-lite-build GitHub Actions: docs GitHub Actions: trigger-sandbox-build ✅ 5 other checks have passed 5/10 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyte/tree/master|master>

by eapolinario

<https://github.com/flyteorg/flyte/commit/d391691c6db314da7298520e4fc83b2f5fe01eb9|d391691c>

- Update Flyte components (#3677) flyteorg/flyte

Release - Flyte v1.6.0 milestone release New release published by flyte-bot Flyte v1.6.0 release In this release we're announcing support for writing backend plugins in python. This is in experimental state, feedback and bug reports are welcome! Database migrations This release contains a database migration that remediates an issue that we discovered with very old installations of Flyte. For more details, please read the Flyte [https://github.com/flyteorg/flyte/releases/tag/v1.5.1](1.5.1 release notes). Platform As mentioned in the previous release, we are working to improve performance investigations. In this release we're announcing: 1. Runtime metrics UI 2. Profile time spent in a task via @timeit decorator 3. Lazy loading of flytekit dependencies flytekit Lots of features shipped in 1.6, including: 1. Prettified pyflyte run logs 2. Simplified image builds via ImageSpec 3. External backed plugins For a full changelog, go to https://github.com/flyteorg/flytekit/releases/tag/v1.6.0. Console • feat: show launchplan in execution table by @pradithya in flyteorg/flyteconsole#738 • feat: show launch plan information in workflow's schedules by @pradithya in flyteorg/flyteconsole#739 • fix: passthrough runtime env vars by @ursucarina in flyteorg/flyteconsole#741 • chore: add fallback to task execution link by @ursucarina in flyteorg/flyteconsole#743 • chore: allow custom subnav by @ursucarina in flyteorg/flyteconsole#734 • fix: force node executions to pull their status by @ursucarina in flyteorg/flyteconsole#737 • chore: fix details panel card padding by @ursucarina in flyteorg/flyteconsole#745 • chore: fix crash by @ursucarina in flyteorg/flyteconsole#746 • [UI Feature] Add full-list log output to execution detail panel by @james-union in flyteorg/flyteconsole#744 • TLM add log-message window to left panel by @james-union in flyteorg/flyteconsole#748 • [Snyk] Upgrade eslint from 8.31.0 to 8.33.0 by @EngHabu in flyteorg/flyteconsole#695 • chore: [tlm] comprehensive node execution query by @ursucarina in flyteorg/flyteconsole#749 • chore: guard against /tasks failing by @ursucarina in flyteorg/flyteconsole#750 • chore: propagate dynamic parent id by @ursucarina in flyteorg/flyteconsole#751 • Add support fetching description entity by @pingsutw in flyteorg/flyteconsole#735 Admin • Infer GOOS and GOARCH from environment by @jeevb in flyteorg/flyteadmin#550 • Enrich TerminateExecution error to tell propeller the execution already terminated by @EngHabu in flyteorg/flyteadmin#551 • Address resolution by @wild-endeavor in flyteorg/flyteadmin#546 • Add migration to turn

parent_id

column into

bigint

only if necessary by @eapolinario in flyteorg/flyteadmin#554 Propeller • Moved controller-runtime start out of webhook Run function by @hamersaw in flyteorg/flytepropeller#546 • Fixing recovering of SKIPPED nodes by @hamersaw in flyteorg/flytepropeller#551 • Remove resource injection on the node for container task by @ByronHsu in flyteorg/flytepropeller#544 • Infer GOOS and GOARCH from environment by @jeevb in flyteorg/flytepropeller#552 • fix makefile to read variables from environment and overrides by @jeevb in flyteorg/flytepropeller#554 • Remove BarrierTick by @hamersaw in flyteorg/flytepropeller#545 • Check for TerminateExecution error and eat Precondition status by @EngHabu in flyteorg/flytepropeller#553 • Setting primaryContainerName by default on Pod plugin by @hamersaw in flyteorg/flytepropeller#555 • Implement ability to specify additional/override annotations when using Vault Secret Manager by @pradithya in flyteorg/flytepropeller#556 • Maintaining Interruptible and OverwriteCache for reference launchplans by @hamersaw in flyteorg/flytepropeller#557 • Added support for aborting task nodes reported as failures by @hamersaw in flyteorg/flytepropeller#541 • Added support for EnvironmentVariables on ExecutionConfig by @hamersaw in flyteorg/flytepropeller#558 • Fast fail if task resource requests exceed k8s resource limits by @hamersaw in flyteorg/flytepropeller#488 New Contributors • @wckdman made their first contribution in flyteorg/flytekit#1588 • @peridotml made their first contribution in flyteorg/flytekit#1599 • @ringohoffman made their first contribution in flyteorg/flytekit#1631 • @elibixby made their first contribution in flyteorg/flytekit#1615 • @ByronHsu made their first contribution in flyteorg/flytepropeller#544 flyteorg/flyte

Deployment to github-pages by flyte-bot flyteorg/flyte

#1636 Fetch task executions in dynamic Pull request opened by pingsutw TL;DR Fixes flyteorg/flyte#3639 Instead of fetching flyte task entity from admin, we should get task interface from DynamicWorkflowNodeMetadata. btw, the sub node data in the dynamic has been add into the

node_mapping

. we can directly get task interface from the node_mapping Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☑︎ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description ^^^ Tracking Issue ^^^ Follow-up issue NA flyteorg/flytekit GitHub Actions: build-plugins (3.8, flytekit-modin) GitHub Actions: build-plugins (3.8, flytekit-mlflow) GitHub Actions: build-plugins (3.8, flytekit-kf-tensorflow) GitHub Actions: build-plugins (3.8, flytekit-kf-pytorch) GitHub Actions: build-plugins (3.8, flytekit-kf-mpi) GitHub Actions: build-plugins (3.8, flytekit-k8s-pod) GitHub Actions: build-plugins (3.8, flytekit-hive) GitHub Actions: build-plugins (3.8, flytekit-greatexpectations) GitHub Actions: build-plugins (3.8, flytekit-envd) GitHub Actions: build-plugins (3.8, flytekit-duckdb) GitHub Actions: build-plugins (3.8, flytekit-dolt) GitHub Actions: build-plugins (3.8, flytekit-deck-standard) GitHub Actions: build-plugins (3.8, flytekit-dbt) GitHub Actions: build-plugins (3.8, flytekit-data-fsspec) GitHub Actions: build-plugins (3.8, flytekit-dask) GitHub Actions: build-plugins (3.8, flytekit-bigquery) GitHub Actions: build-plugins (3.8, flytekit-aws-sagemaker) GitHub Actions: build-plugins (3.8, flytekit-aws-batch) GitHub Actions: build-plugins (3.8, flytekit-aws-athena) GitHub Actions: lint GitHub Actions: build (windows-latest, 3.11) GitHub Actions: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.11) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: build (ubuntu-latest, 3.8) GitHub Actions: Docs Warnings GitHub Actions: docs ✅ 1 other check has passed 1/30 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by pingsutw

<https://github.com/flyteorg/flytekit/commit/dab1eed3b3dc29e2587c2473ede218ab97c904a4|dab1eed3>

- Multi arch imageSpec (#1630) flyteorg/flytekit

#3679 [FlyteCTL Feature] `get task --version` filters all tasks by version Issue created by tekumara Describe the feature/command for FlyteCTL Current behaviour: ``` ❯ flytectl get task -p flytesnacks -d development --version v3 --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | VERSION (15) | NAME | TYPE | INPUTS | OUTPUTS | DISCOVERABLE | DISCOVERY VERSION | CREATED AT | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v3 | aircraft.etl_flow.load_live_data | python-task | live_aircraft_data | | | | 2023-05-13T130328.197109Z | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v3 | aircraft.etl_flow.load_reference_data | python-task | airlines | | | | 2023-05-13T130328.189977Z | | | | | airports | | | | | | | | | routes | | | | | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v3 | aircraft.etl_flow.transform | python-task | airlines | o0 | | | 2023-05-13T130328.182702Z | | | | | raw_aircraft_data | | | | | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v3 | aircraft.etl_flow.extract_live_data | python-task | | o0 | | | 2023-05-13T130328.173540Z | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v3 | aircraft.etl_flow.extract_reference_data | python-task | | airlines | | | 2023-05-13T130328.159936Z | | | | | | airports | | | | | | | | | routes | | | | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v2 | aircraft.etl_flow.load_live_data | python-task | live_aircraft_data | | | | 2023-05-13T123917.548179Z | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v2 | aircraft.etl_flow.load_reference_data | python-task | airlines | | | | 2023-05-13T123917.540335Z | | | | | airports | | | | | | | | | routes | | | | | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v2 | aircraft.etl_flow.transform | python-task | airlines | o0 | | | 2023-05-13T123917.531564Z | | | | | raw_aircraft_data | | | | | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v2 | aircraft.etl_flow.extract_live_data | python-task | | o0 | | | 2023-05-13T123917.523488Z | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v2 | aircraft.etl_flow.extract_reference_data | python-task | | airlines | | | 2023-05-13T123917.508720Z | | | | | | airports | | | | | | | | | routes | | | | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v1 | aircraft.etl_flow.load_live_data | python-task | live_aircraft_data | | | | 2023-05-13T052448.797097Z | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v1 | aircraft.etl_flow.load_reference_data | python-task | airlines | | | | 2023-05-13T052448.787874Z | | | | | airports | | | | | | | | | routes | | | | | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v1 | aircraft.etl_flow.transform | python-task | airlines | o0 | | | 2023-05-13T052448.779707Z | | | | | raw_aircraft_data | | | | | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v1 | aircraft.etl_flow.extract_live_data | python-task | | o0 | | | 2023-05-13T052448.771175Z | --------------- ------------------------------------------ ------------- -------------------- ---------- -------------- ------------------- ----------------------------- | v1 | aircraft.etl_flow.extract_reference_data | python-task | | airlines | | | 2023-05-13T052448.756913Z | | | | | | airports | | … flyteorg/flyte

#3680 [flytekit feature] Support Pandas 2 Issue created by tekumara Motivation: Why do you think this is important? I'd like to use Pandas 2 in my tasks because it has a lot of performance improvements. But I'm limited to <2 because Flytekit pins to pandas&gt;=1.0.0,&lt;2.0.0. Goal: What should the final outcome look like, ideally? I can use Pandas 2 in my tasks. Describe alternatives you've considered Not using Pandas 2. Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3681 [BUG] Flytekit type hints are ignored by mypy Issue created by tekumara Describe the bug Flytekit type hints are ignored by mypy because flytekit does not have a

py.typed

marker as per PEP 0561 Expected behavior Usage of flytekit is checked against its types. Additional context to reproduce Given

from typing import Dict, List, NamedTuple

from flytekit import task


class OpenFlightsData(NamedTuple):
    routes: List[Dict[str, str]]
    airlines: Dict[str, str]
    airports: Dict[str, Dict[str, str]]


@task()
def extract_reference_data() -> OpenFlightsData:
    return OpenFlightsData(
        routes=[{"MAO": "CIZ"}], airlines={"0B": "Blue Air"}, airports={"AAA": {"lat": "1", "lon": "2"}}
    )

Then when running mypy 1.3.0:

❯ mypy aircraft/test.py
aircraft/test.py:3: error: Skipping analyzing "flytekit": module is installed, but missing library stubs or py.typed marker  [import]
aircraft/test.py:3: note: See <https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports>
Found 1 error in 1 file (checked 1 source file)

Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3682 [BUG] flytekit 1.6.0 task function calls do not type check Issue created by tekumara Describe the bug In flyteorg/flytekit#1631 the

task

return type was changed to effectively

Tuple[Promise] | Promise | VoidPromise | Tuple[Unknown, ...] | None

. This breaks usage of tasks in type checkers like pyright / vscode. Expected behavior Task function calls still type check correctly, as they did in flytekit 1.5.0 Additional context to reproduce This type checks without errors in flytekit 1.5.0:

from typing import Dict, List, NamedTuple

import pandas as pd
from flytekit import task, workflow


class OpenFlightsData(NamedTuple):
    routes: List[Dict[str, str]]
    airlines: Dict[str, str]
    airports: Dict[str, Dict[str, str]]


@task()
def extract_reference_data() -> OpenFlightsData:
    return OpenFlightsData(
        routes=[{"MAO": "CIZ"}], airlines={"0B": "Blue Air"}, airports={"AAA": {"lat": "1", "lon": "2"}}
    )


@task()
def extract_live_data() -> pd.DataFrame:
    return pd.DataFrame()


@task()
def transform(raw_aircraft_data: pd.DataFrame, airlines: Dict[str, str]) -> pd.DataFrame:
    # do stuff ..
    return pd.DataFrame()


@workflow
def main() -> None:
    reference_data = extract_reference_data()
    reveal_type(reference_data)   # expecting OpenFlightsData
    live_data = extract_live_data()
    reveal_type(live_data)        # expecting Dataframe

    transform(raw_aircraft_data=live_data, airlines=reference_data.airlines)


if __name__ == "__main__":
    main()

With flytekit 1.6.0 and pyright / vscode:

❯ pyright test.py
test.py
  test.py:34:17 - information: Type of "reference_data" is "Tuple[Promise] | Promise | VoidPromise | Tuple[Unknown, ...] | None"
  test.py:36:17 - information: Type of "live_data" is "Tuple[Promise] | Promise | VoidPromise | Tuple[Unknown, ...] | None"
  test.py:38:68 - error: Cannot access member "airlines" for type "Tuple[Promise]"
    Member "airlines" is unknown (reportGeneralTypeIssues)
  test.py:38:68 - error: Cannot access member "airlines" for type "Promise"
    Member "airlines" is unknown (reportGeneralTypeIssues)
  test.py:38:68 - error: Cannot access member "airlines" for type "VoidPromise"
    Member "airlines" is unknown (reportGeneralTypeIssues)
  test.py:38:68 - error: Cannot access member "airlines" for type "Tuple[Unknown, ...]"
    Member "airlines" is unknown (reportGeneralTypeIssues)
  test.py:38:68 - error: "airlines" is not a known member of "None" (reportOptionalMemberAccess)
5 errors, 0 warnings, 2 informations

Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#1637 feat: add py.typed Pull request opened by tekumara TL;DR Add

py.typed

file so that when type checkers are run in codebases that use flytekit, its types will be checked. Resolves flyteorg/flyte#3681 Type ☐ Bug Fix ☑︎ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description Add

py.typed

file Tracking Issue flyteorg/flyte#3681 flyteorg/flytekit GitHub Actions: build-plugins (3.8, flytekit-pandera) GitHub Actions: build-plugins (3.8, flytekit-onnx-scikitlearn) GitHub Actions: build-plugins (3.8, flytekit-onnx-pytorch) GitHub Actions: build-plugins (3.8, flytekit-modin) GitHub Actions: build-plugins (3.8, flytekit-mlflow) GitHub Actions: build-plugins (3.8, flytekit-kf-tensorflow) GitHub Actions: build-plugins (3.8, flytekit-kf-pytorch) GitHub Actions: build-plugins (3.8, flytekit-kf-mpi) GitHub Actions: build-plugins (3.8, flytekit-k8s-pod) GitHub Actions: build-plugins (3.8, flytekit-hive) GitHub Actions: build-plugins (3.8, flytekit-greatexpectations) GitHub Actions: build-plugins (3.8, flytekit-envd) GitHub Actions: build-plugins (3.8, flytekit-duckdb) GitHub Actions: build-plugins (3.8, flytekit-dolt) GitHub Actions: build-plugins (3.8, flytekit-deck-standard) GitHub Actions: build-plugins (3.8, flytekit-dbt) GitHub Actions: build-plugins (3.8, flytekit-data-fsspec) GitHub Actions: build-plugins (3.8, flytekit-dask) GitHub Actions: build-plugins (3.8, flytekit-bigquery) GitHub Actions: build-plugins (3.8, flytekit-aws-sagemaker) GitHub Actions: build-plugins (3.8, flytekit-aws-batch) GitHub Actions: build-plugins (3.8, flytekit-aws-athena) GitHub Actions: build (windows-latest, 3.11) GitHub Actions: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.11) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: build (ubuntu-latest, 3.8) GitHub Actions: Docs Warnings ✅ No checks have passed 0/30 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by pingsutw

<https://github.com/flyteorg/flytekit/commit/8ef79e535521500a4de6b84de268b323a580129b|8ef79e53>

- Add executor_path and applications_path to spark config (#1634) flyteorg/flytekit

#561 [Doc] Add Go / dependencies installation instructions Pull request opened by kevin85421 TL;DR as title Type ☐ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue The instructions are similar to: https://github.com/ray-project/kuberay/blob/master/ray-operator/DEVELOPMENT.md#use-go-v117. Complete description as title Tracking Issue NA Follow-up issue NA flyteorg/flytepropeller GitHub Actions: End2End Test / End to End tests GitHub Actions: Lint / Run Lint DCO: DCO ✅ 8 other checks have passed 8/11 successful checks

#1638 feat: Add audience token for Auth0 ClientCredentials Auth Flow Pull request opened by PudgyPigeon TL;DR This PR enables passing in the

audience

parameter into the

get_token

method - via the ClientCredentials flow and the ClientConfig object. Also adds in the ability for Pyflyte/Flytekit to read in the audience from the config.yaml file, but it is not linked to the get_token method (only ClientConfig object params are used at the moment). Type • [ x ] Bug Fix • [ x ] Feature ☐ Plugin Are all requirements met? • [ x ] Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added • [ x ] Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Auth0 requires an audience parameter for its various requests. This was previously not enabled in the Flytekit source code. This PR adds support for that by piping in the

audience

parameter as input from FlyteAdmin's audience field, and then into the various functions/methods/classes that handle the auth request. The ability to pipe in "audience" from the config.yaml file is also enabled so set up is there for enabling this method of defining the parameter, but it's fine if it gets deleted as the ClientConfig inferring audience from Admin works. Tracking Issue flyteorg/flyte#3661 Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit DCO: DCO ✅ 1 other check has passed 1/2 successful checks

#1639 feat: Add Auth0/audience support for ClientCredentials flow Pull request opened by PudgyPigeon TL;DR This PR enables passing in the

audience

parameter into the

get_token

method - via the ClientCredentials flow and the ClientConfig object. Also adds in the ability for Pyflyte/Flytekit to read in the audience from the config.yaml file, but it is not linked to the get_token method (only ClientConfig object params are used at the moment). Type • [ x ] Bug Fix • [ x ] Feature ☐ Plugina Are all requirements met? • [ x ] Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added • [ x ] Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Auth0 requires an audience parameter for its various requests. This was previously not enabled in the Flytekit source code. This PR adds support for that by piping in the

audience

parameter as input from FlyteAdmin's audience field, and then into the various functions/methods/classes that handle the auth request. The ability to pipe in "audience" from the config.yaml file is also enabled so set up is there for enabling this method of defining the parameter, but it's fine if it gets deleted as the ClientConfig inferring audience from Admin works. Tracking Issue flyteorg/flyte#3661 Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit ✅ All checks have passed 2/2 successful checks

#3684 [Housekeeping] go-gormigrate/gormigrate is abandoned Issue created by honnix Describe the issue flyteadmin uses https://github.com/go-gormigrate/gormigrate for database migration, and unfortunately this repo has been abandoned by the author (see go-gormigrate/gormigrate#180 (comment) for the reason). We might want to take some action to mitigate this. What if we do not do this? It is probably OK for now because the features we use in flyteadmin should be minimum and there doesn't seem to be any urgent bug fixes, etc. But in the long run, it is not sustainable to depend on an unmaintained lib for critical things like DB migration. Related component(s) flyteadmin Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3685 Support latest vaex-core Issue created by tekumara Motivation: Why do you think this is important? To support efficient installation in python 3.10. flytekitplugins-vaex pins to vaex-core&gt;=4.13.0,&lt;4.14 which doesn't have wheels for python 3.10. This means we need to build wheels ourselves to use flytekitplugins-vaex on python 3.10. vaex-core 4.16.1 has wheels for python 3.10 Goal: What should the final outcome look like, ideally? flytekitplugins-vaex installs from wheels. Describe alternatives you've considered Building our own wheels. Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flyte/tree/master|master>

by jeevb

<https://github.com/flyteorg/flyte/commit/4b1f0a2c5e1c8ede233c0c8622f243b44122e7a8|4b1f0a2c>

- feat: Allow "audience" param to be set in values.yaml - Flyte-Binary (000-core.yaml) (#3683) flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by pingsutw

<https://github.com/flyteorg/flytekit/commit/b410108887b76b5afcd7cfd36aaeda7540737513|b4101088>

- Add support for env vars to pyflyte run (#1617) flyteorg/flytekit

#1640 [WIP] - Array node map task Pull request opened by eapolinario TL;DR This PR adds support for map tasks defined in terms of ArrayNode TODO ☐ correctly set node in input bindings ☐ include metadata in hash so

map_task(a_mappable_task)

and

map_task(a_mappable_task, concurrency=2)

may both be used at the same time ☐ retries hard-coded to 1 on the node-level so task-level not used ☐ support for partials Type ☐ Bug Fix ☑︎ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description Extremely WIP at the moment. Need to verify support for container tasks and other backend entities. Tracking Issue flyteorg/flyte#1131 Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit WIP: Title contains &quot;WIP&quot; ✅ 1 other check has passed 1/2 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyteconsole/tree/master|master>

by ursucarina

<https://github.com/flyteorg/flyteconsole/commit/22ed97fc892d1fa2575746106dfc2f9bdcd68ba2|22ed97fc>

- Export Flytedecks support for TLRO (#757) flyteorg/flyteconsole

1 new commit pushed to

<https://github.com/flyteorg/flytesnacks/tree/master|master>

by hamersaw

<https://github.com/flyteorg/flytesnacks/commit/b3f67cdc22a2528ccf10c1eb6f8ad09caa65fd3e|b3f67cdc>

- Update vault secret manager documentation and add example (#990) flyteorg/flytesnacks

Pending review on flyteorg/flytekit-python-template - Manage reminder [#33] Integration testing suite v1 (zeryx) 4 days stale · 11 days old · Waiting on _ eapolinario, @Niels Bantilan, pingsutw_

Pending review on flyteorg/flytekit-java - Manage reminder [#6] Update .env.local in README (kanterov) a year stale · 3 years old · Waiting on _ @Ketan (kumare3)_

1 new commit pushed to

<https://github.com/flyteorg/flyteadmin/tree/master|master>

by wild-endeavor

<https://github.com/flyteorg/flyteadmin/commit/610451d21ca2fa8f598ebc26b8ebb96e423e270a|610451d2>

- Inject user identifier to ExecutionSpec (#549) flyteorg/flyteadmin

#549 Inject user identifier to ExecutionSpec Pull request opened by ByronHsu TL;DR This pr provides a middleware to inject user identifier to ExecutionSpec. By default, the value of the user identifier is userid from access/id token. Users can customize their own middleware and inject different values. Type ☐ Bug Fix ☑︎ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☑︎ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Tracking Issue flyteorg/flyte#3566 flyteorg/flyteadmin GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Goreleaser GitHub Actions: Build & Push Flyteadmin Image GitHub Actions: Bump Version ✅ 10 other checks have passed 10/14 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyte/tree/master|master>

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/6fd4ddb5354314038a85ddb32375da1aa077bd3b|6fd4ddb5>

- feat: allow seedProjects to be set via inline configuration (#3631) flyteorg/flyte