1 new commit pushed to

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

by github-actions[bot]

<https://github.com/flyteorg/flytekit-java/commit/707398f90c32578e59b28529d59d74f26cdeaa2d|707398f9>

- [maven-release-plugin] prepare for next development iteration flyteorg/flytekit-java

Release - 0.4.15 New release published by honnix The same as 0.4.14 flyteorg/flytekit-java

#3556 [Housekeeping] Add ggydush to flytekit committers Issue created by wild-endeavor Add ggydush to the https://github.com/orgs/flyteorg/teams/flytekit-committers/members group. flyteorg/flyte

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/01218d2636a30c05b3daf362c335f2b21b793b49|01218d26>

- persisting k8s plugin state between evaluations (#540) flyteorg/flytepropeller

#3557 [BUG] Unnecessary warning in response to every pyflyte command Issue created by tsheiner Describe the bug 1. execute any valid pyflyte command 2. see in response the following warning

{"asctime": "2023-03-30 10:54:22,803", "name": "flytekit", "levelname": "WARNING", "message": "FlyteSchema is deprecated, use Structured Dataset instead."}

Expected behavior That I only get this warning if I am doing something that involves FlyteSchema Additional context to reproduce No response Screenshots 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/flyteconsole/tree/master|master>

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/ca1b5b83e7177efd941e0c29b0c539fc610dfa87|ca1b5b83>

- gate node in dynamic task (#729) flyteorg/flyteconsole

#3354 [BUG] [CONSOLE] gate node in dynamic task Issue created by wild-endeavor Describe the bug Gate nodes inside of dynamic tasks don't behave the same. This workflow https://github.com/flyteorg/flytesnacks/blob/cecf8b1c98b784da3f15c1ab04624619890d1d16/cookbook/core/control_flow/human_in_the_loop.py#L82 is functionally the same as the

mainwf

that we've been testing on, except that it happens inside a dynamic task instead of the top level workflow. However when run inside a dynamic workflow, things don't look the same. None of the gate node stuff is there and the approval node only shows Running not Paused. Expected behavior Things should look the same as the non-dynamic case. This includes all views (node-list, graph, timeline) Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

Release - v1.1.74 New release published by flyte-bot Changelog • 01218d2 persisting k8s plugin state between evaluations (#540) flyteorg/flytepropeller

#547 [Snyk] Security upgrade alpine from 3.13.7 to 3.14 Pull request opened by eapolinario This PR was automatically created by Snyk using the credentials of a real user. Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image. Changes included in this PR • boilerplate/flyte/golang_dockerfile/Dockerfile.GoTemplate We recommend upgrading to

alpine:3.14

, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected. Some of the most important vulnerabilities in your base image include: * * * Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs. For more information: https://camo.githubusercontent.com/a181da9b8d903a5b93ab84f1a9e0434cafbd927f88695cc88b2ba64ccc456fb9/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f69497a5a6a646c5a47526c4d69316d596a63334c5451785a4449744f5441304f43316b4f5459354d7a426c4e5759355a6a4d694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a4e6d4e32566b5a4755794c575a694e7a63744e44466b4d6930354d4451344c5751354e6a6b7a4d4755315a6a6c6d4d794a3966513d3d 🧐 View latest project report 🛠️ Adjust project settings * * * Learn how to fix vulnerabilities with free interactive lessons: 🦉 Learn about vulnerability in an interactive lesson of Snyk Learn. flyteorg/flyteadmin GitHub Actions: Goreleaser GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Build & Push Flyteadmin Image GitHub Actions: Bump Version Codecov: 58.81% (-0.04%) compared to eb695b1 DCO: DCO ✅ 8 other checks have passed 8/14 successful checks

1 new commit pushed to

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

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/c82e7556250582d315d3f6cb3edafb7ab2a16fdf|c82e7556>

- fix: type error on invalid nested json input (#693) flyteorg/flyteconsole

#3157 [BUG] TypeError: can't convert null to object if using wrong default in dataclass Issue created by fellhorn Describe the bug When trying to launch a workflow with a faulty

dataclass

the UI breaks with an unhelpful react error as shown in the screenshot:

The error we received was:
TypeError: can't convert null to object

There may be additional information in the browser console.

Please find this minimal example workflow:

from typing import Optional, Dict

from dataclasses import dataclass
from dataclasses_json import dataclass_json
from flytekit import task, workflow


@dataclass_json
@dataclass
class MyConfig:
    k: Optional[Dict] = None


@task
def t1(a: MyConfig) -> str:
    if a.k and "foo" in a.k:
        return a.k["foo"]
    else:
        return "42"


@workflow
def my_wf(a: MyConfig = MyConfig()) -> str:
    x = t1(a=a)
    return x

where

k

has a wrong default. Instead of

k: Optional[Dict] = None

, it should be

from dataclasses import field

@dataclass_json
@dataclass
class MyConfig:
    k: Optional[Dict] = field(default_factory=lambda: {})

Expected behavior I am aware of the error on the user side. Still: I think flyte could show a more helpful error message here to point to the bad parameter. Additional context to reproduce The error shown in the browser dev console is:

TypeError: can't convert null to object
**REDACTED**
 
Object { componentStack: "\n    in Unknown\n    in div\n    in S\n    in section\n    in ForwardRef\n    in div\n    in ForwardRef\n    in ForwardRef\n    in Unknown\n    in Unknown\n    in div\n    in ForwardRef\n    in ForwardRef\n    in div\n    in t\n    in ForwardRef\n    in s\n    in div\n    in ForwardRef\n    in ForwardRef\n    in ForwardRef\n    in ForwardRef\n    in Unknown\n    in E\n    in Unknown\n    in Unknown\n    in Unknown\n    in E\n    in div\n    in Unknown\n    in Unknown\n    in t\n    in t\n    in Unknown\n    in E\n    in t\n    in div\n    in t\n    in Unknown\n    in l\n    in c\n    in l\n    in Unknown\n    in Unknown\n    in Unknown" }
main-965d5331.js:1:369655

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

Release - v1.5.4 New release published by flyte-bot 1.5.4 (2023-03-30) Bug Fixes • type error on invalid nested json input (#693) (c82e755), closes #692 flyteorg/flyteconsole

#547 Add support for GCP secret manager Pull request opened by jeevb Tested with:

from flytekit import Secret, task, workflow


@task(secret_requests=[Secret(group="mainsecret", key="na", group_version="1")])
def secret_task() -> str:
    with open("/etc/flyte/secrets/mainsecret/1") as f:
        return f.read()


@workflow
def wf() -> str:
    x = secret_task()
    return x

Note the use of the required

key

, even though the secrets plugin does not use it. @Yee: we may want to consider making this optional. Flytekit will also need support for including the group version in the file path when fetching secrets. flyteorg/flytepropeller GitHub Actions: Goreleaser GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Bump Version ✅ 11 other checks have passed 11/14 successful checks

#1571 Support GCP secrets Pull request opened by wild-endeavor TL;DR Support GCP secret style. Make the key optional now in Secret since GCP doesn't have a key. But it does have a group version so add that to the env var and file path lookups. Order is group -> group version (if present) -> key (if present) Backend PR flyteorg/flytepropeller#547 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 https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

#3558 [RFC] External Plugin Service Pull request opened by pingsutw Describe your changes Add RFC for External Plugin Service. Hackmd flyteorg/flyte GitHub Actions: generate_helm GitHub Actions: docs GitHub Actions: generate_kustomize GitHub Actions: compile ✅ 2 other checks have passed 2/6 successful checks

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flytepropeller/commit/f88f165ccf8f9896223dfc61936948fda3de29e4|f88f165c>

- Add support for GCP secret manager (#547) flyteorg/flytepropeller

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flytekit/commit/9658b02fc674db1f89db4fda64c988a153953ca3|9658b02f>

- Support GCP secrets (#1571) flyteorg/flytekit

Release - v1.1.75 New release published by flyte-bot Changelog • f88f165 Add support for GCP secret manager (#547) flyteorg/flytepropeller

#386 Refactor kf-operator plugins configs and support setting different specs for different replica groups Pull request opened by yubofredwang TL;DR This PR refactors config fields for kubeflow operator plugins including: TFJob, MPIJob, PyTorchJob. This change is backward incompatible, so we will keep the original plugin configs untouched and use the new configs in v2 version of the plugins. 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 Code change includes: 1. Move TFJob, MPIJob, PyTorchJob from

flyteidl/plugins/

to

flyteidl/plugins/kubeflow/

2. Create

flyteidl/plugins/kubeflow/common.proto

that contains the definition RestartPolicy, RunPolicy and CleanPodPolicy 3. Add

xxxReplicaSpec

in each job type to allow settings of

replicas

,

image

,

resources

and

restart_policy

Tracking Issue fixes flyteorg/flyte#3308 Follow-up issue flyteorg/flyteidl ✅ All checks have passed 2/2 successful checks

#3559 [BUG] ShellTask error is recognize as system failure Issue created by pradithya Describe the bug Error while executing script within a ShellTask is recognize as system error Expected behavior Error while executing script in ShellTask should be classified as non-system error Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#1572 Improve authoring structure documentation Pull request opened by samhita-alla TL;DR This PR improves the authoring structure documentation. • Added graphviz package to render visualizations • Edited content for clarity 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 https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

#3560 [BUG] ContainerTask does not accept a task_config Issue created by vkaiser-mb Describe the bug As described in the docu, flytekit.ContainerTask should be able to accept a

task_config

argument. Currently this fails with:

Failed with Unknown Exception <class 'TypeError'> Reason: __init__() got multiple values for keyword argument 'task_config'
__init__() got multiple values for keyword argument 'task_config'

Expected behavior This code should execute without any error message:

from flytekitplugins.pod import Pod
from kubernetes.client.models import V1PodSpec


from flytekit import ContainerTask, workflow, kwtypes, Resources

TC = Pod(
    pod_spec=V1PodSpec(
        containers=[],
        node_selector={"key": "value"},
    )
)

ct_task = ContainerTask(
    name="ellipse-area-metadata-shell",
    task_config=TC,
    input_data_dir="/var/inputs",
    output_data_dir="/var/outputs",
    inputs=kwtypes(a=float, b=float),
    outputs=kwtypes(area=float, metadata=str),
    image="<http://ghcr.io/flyteorg/rawcontainers-shell:v2|ghcr.io/flyteorg/rawcontainers-shell:v2>",
    command=[
        "./calculate-ellipse-area.sh",
        "{{.inputs.a}}",
        "{{.inputs.b}}",
        "/var/outputs",
    ],
    requests=Resources(
        cpu="100m",
        mem="1G",
    ),
)


@workflow
def wf():
    ct_task

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

#3055 [Core feature] support pod plugin for ContainerTasks Issue created by flixr Motivation: Why do you think this is important? ContainerTasks currently don't support the pod plugin so we can't use it to control the pod and e.g. mount additional volumes or inject env vars and secrets. Goal: What should the final outcome look like, ideally? ContainerTask supports specifying pod spec. Describe alternatives you've considered Not using flyte... 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

#3518 Split flyte-binary services into http and grpc, and some cleanups Pull request opened by jeevb flyteorg/flyte ✅ All checks have passed 11/11 successful checks

#3513 Test sandbox with Kong ingress controller Pull request opened by jeevb on <!date^1679438902^{date_short}|2023-03-21T22:48:22Z> flyteorg/flyte DCO: DCO ✅ 10 other checks have passed 10/11 successful checks

#3561 Render flyte-sandbox manifests to pick up any changes to flyte-binary chart during automation Pull request opened by jeevb flyteorg/flyte ✅ All checks have passed 6/6 successful checks

#3562 Community page updates Pull request opened by davidmirror-ops Tracking issue Describe your changes Fixing broken links Check all the applicable boxes ☐ I updated the documentation accordingly. ☐ All new and existing tests passed. ☐ All commits are signed-off. Screenshots Note to reviewers flyteorg/flyte ✅ All checks have passed 6/6 successful checks

#3 Update Contributor role privileges Issue created by davidmirror-ops Currently, the Contributor role privileges include direct branching into the repo. In order to establish a gradual assignation of permissions, Contributors should only be allowed to submit PRs from forks, while keeping the branching permissions for Maintainers and above flyteorg/community

#978 Exclude auto-generated style tag from sphinx-prompt Pull request opened by cosmicBboy fixes #3551 flyteorg/flytesnacks ✅ All checks have passed 3/3 successful checks