#4506 Bug/abort map task subtasks Pull request opened by pvditt Tracking issue Docs link Describe your changes Check all the applicable boxes ☐ I updated the documentation accordingly. ☐ All new and existing tests passed. ☐ All commits are signed-off. Setup Process Screenshots Note to reviewers Related PRs flyteorg/flyte Codecov: 59.58% (-0.24%) compared to 956b24e Codecov: 15.62% of diff hit (target 59.81%) GitHub Actions: Lint (flyteplugins) / Run Lint ✅ 27 other checks have passed 27/30 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytekit/commit/b12c84796d7365ffb1b4dce579e35d20906d00f6|b12c8479>

- Fix default paramaters when launching launchplans from within other workflows (#1972) flyteorg/flytekit

#4308 Add support failure node Pull request opened by pingsutw Describe your changes • Compile failure node • Add FailureNodeLookup • Update Failure node binding. • Transition workflow status to

WorkflowPhaseHandlingFailureNode

if workflow fails and workflow has a failureNode. • Transition subworkflow status to

running

if subworkflow has a failureNode and subworkflow fails. Example Three workflows 1. wf1: both workflow and subworkflow have a failure node. propeller will create two tasks when failing 2. wf2: Only one workflow has a failure node. propeller will create one task when failing 3. wf3: failure node is a workflowNode. propeller will create another workflow when failing

flytectl demo start --dev
make compile  # compile the single binary
flyte start --config flyte-single-binary-local.yaml
pip install git+<https://github.com/flyteorg/flytekit.git@2582a8bc16f80ab3a7101af8360e9d7212236e43>
pyflyte run --remote workflow.py wf

import typing
from click.testing import CliRunner

from flytekit import task, workflow, ImageSpec, WorkflowFailurePolicy
from flytekit.clis.sdk_in_container import pyflyte
from flytekit.types.error.error import FlyteError

new_flytekit = "git+<https://github.com/flyteorg/flytekit.git@5a415107b0aff272a16eb147860a65d47a10c4d8>"
image_spec = ImageSpec(packages=[new_flytekit], apt_packages=["git"], registry="pingsutw")


@task(container_image=image_spec)
def create_cluster(name: str):
    print(f"Creating cluster: {name}")


@task(container_image=image_spec)
def t1(a: int, b: str):
    print(f"{a} {b}")
    raise ValueError("Fail!")


@task(container_image=image_spec)
def delete_cluster(name: str, err: typing.Optional[FlyteError] = None):
    print(f"Deleting cluster {name}")
    print(err)


@task(container_image=image_spec)
def clean_up(name: str, err: typing.Optional[FlyteError] = None):
    print(f"Deleting cluster {name} due to {err}")
    print(err)


@workflow(on_failure=clean_up, failure_policy=WorkflowFailurePolicy.FAIL_AFTER_EXECUTABLE_NODES_COMPLETE)
def subwf(name: str = "kevin"):
    c = create_cluster(name=name)
    t = t1(a=1, b="2")
    d = delete_cluster(name=name)
    c >> t >> d


@workflow(on_failure=clean_up, failure_policy=WorkflowFailurePolicy.FAIL_AFTER_EXECUTABLE_NODES_COMPLETE)
def wf1(name: str = "kevin"):
    c = create_cluster(name=name)
    subwf(name="pingsutw")
    t = t1(a=1, b="2")
    d = delete_cluster(name=name)
    c >> t >> d


@workflow(on_failure=clean_up, failure_policy=WorkflowFailurePolicy.FAIL_AFTER_EXECUTABLE_NODES_COMPLETE)
def wf2(name: str = "kevin"):
    c = create_cluster(name=name)
    t = t1(a=1, b="2")
    d = delete_cluster(name=name)
    c >> t >> d


@workflow
def clean_up_wf(name: str = "kevin"):
    return create_cluster(name=name)


@workflow(on_failure=clean_up_wf, failure_policy=WorkflowFailurePolicy.FAIL_AFTER_EXECUTABLE_NODES_COMPLETE)
def wf3(name: str = "Kevin"):
    c = create_cluster(name=name)
    t = t1(a=1, b="2")
    d = delete_cluster(name=name)
    c >> t >> d


if __name__ == '__main__':
    runner = CliRunner()
    result = runner.invoke(pyflyte.main, ["run", "--remote", "failure_node.py", "wf2"])
    print(result.output)

Tracking issue #1506 Screenshots image flyteorg/flyte Codecov: 59.45% (-0.02%) compared to a8f4904 ✅ 29 other checks have passed 29/30 successful checks

1 new commit pushed to

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

by jeevb

<https://github.com/flyteorg/flyte/commit/7481b3d0adc508fe07c5e2aa624621687efd41c4|7481b3d0>

- Correctly handle resource overrides in KF plugins (#4467) flyteorg/flyte

#4508 [BUG] Secrets injection is broken Issue created by eapolinario Describe the bug flyte pod webhook panics while injecting secrets, regardless of the secret manager (k8s, aws, gcp, etc). We see this panic in the logs when executing a task that requires a secret:

{"json":{"exec_id":"f3d082a54f9b94988ba4","node":"workflowsexamplesecrettask","ns":"flytesnacks-development","res_ver":"108245851","routine":"worker-3","src":"controller.go:36","tasktype":"python-task","wf":"flytesnacks:development:.flytegen.workflows.example.secret_task"},"level":"info","msg":"The back-off handler for [/v1, Kind=pod,flytesnacks-development] has been loaded.\n","ts":"2023-11-30T21:26:53Z"}
2023/11/30 21:26:53 http: panic serving 10.2.149.237:48966: runtime error: invalid memory address or nil pointer dereference
goroutine 26608 [running]:
net/http.(*conn).serve.func1()
        /usr/local/go/src/net/http/server.go:1850 +0xbf
panic({0x2f4dc00, 0x6164a90})
        /usr/local/go/src/runtime/panic.go:890 +0x262
<http://sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Decoder).DecodeRaw(0x0|sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Decoder).DecodeRaw(0x0>, {{0xc005ce8000, 0x1b70, 0x2000}, {0x0, 0x0}}, {0x46ca258, 0xc0037b0000})
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.2/pkg/webhook/admission/decode.go:77 +0x15a
<http://sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Decoder).Decode(_|sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Decoder).Decode(_>, {{{0xc00377fcb0, 0x24}, {{0x0, 0x0}, {0xc005fd30c0, 0x2}, {0xc005fd30c2, 0x3}}, {{0x0, ...}, ...}, ...}}, ...)
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.2/pkg/webhook/admission/decode.go:49 +0x8e
<http://github.com/flyteorg/flyte/flytepropeller/pkg/webhook.(*PodMutator).Handle(_|github.com/flyteorg/flyte/flytepropeller/pkg/webhook.(*PodMutator).Handle(_>, {_, _}, {{{0xc00377fcb0, 0x24}, {{0x0, 0x0}, {0xc005fd30c0, 0x2}, {0xc005fd30c2, ...}}, ...}})
        /flyteorg/build/flytepropeller/pkg/webhook/pod.go:86 +0xc8
<http://sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Webhook).Handle(_|sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Webhook).Handle(_>, {_, _}, {{{0xc00377fcb0, 0x24}, {{0x0, 0x0}, {0xc005fd30c0, 0x2}, {0xc005fd30c2, ...}}, ...}})
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.2/pkg/webhook/admission/webhook.go:169 +0x20b
<http://sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Webhook).ServeHTTP(0xc008872a50|sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Webhook).ServeHTTP(0xc008872a50>, {0x7f1ba49b1e40?, 0xc00a05f450}, 0xc005cc0100)
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.2/pkg/webhook/admission/http.go:98 +0xc94
<http://github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerInFlight.func1({0x7f1ba49b1e40|github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerInFlight.func1({0x7f1ba49b1e40>, 0xc00a05f450}, 0x46e7500?)
        /go/pkg/mod/github.com/prometheus/client_golang@v1.16.0/prometheus/promhttp/instrument_server.go:60 +0xd4
net/http.HandlerFunc.ServeHTTP(0x46e7560?, {0x7f1ba49b1e40?, 0xc00a05f450?}, 0x7e1286?)
        /usr/local/go/src/net/http/server.go:2109 +0x2f
<http://github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerCounter.func1({0x46e7560|github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerCounter.func1({0x46e7560>?, 0xc00175bce0?}, 0xc005cc0100)
        /go/pkg/mod/github.com/prometheus/client_golang@v1.16.0/prometheus/promhttp/instrument_server.go:147 +0xc5
net/http.HandlerFunc.ServeHTTP(0x7e0ce5?, {0x46e7560?, 0xc00175bce0?}, 0x40?)
        /usr/local/go/src/net/http/server.go:2109 +0x2f
<http://github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerDuration.func2(|github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerDuration.func2(>{0x46e7560, 0xc00175bce0}, 0xc005cc0100)
        /go/pkg/mod/github.com/prometheus/client_golang@v1.16.0/prometheus/promhttp/instrument_server.go:109 +0xc7
net/http.HandlerFunc.ServeHTTP(0xc00175bce0?, {0x46e7560?, 0xc00175bce0?}, 0x34ec45f?)
        /usr/local/go/src/net/http/server.go:2109 +0x2f
net/http.(*ServeMux).ServeHTTP(0xc00377fc35?, {0x46e7560, 0xc00175bce0}, 0xc005cc0100)
        /usr/local/go/src/net/http/server.go:2487 +0x149
net/http.serverHandler.ServeHTTP({0x46cec18?}, {0x46e7560, 0xc00175bce0}, 0xc005cc0100)
        /usr/local/go/src/net/http/server.go:2947 +0x30c
net/http.(*conn).serve(0xc000c6a8c0, {0x46e9780, 0xc008ab12f0})
        /usr/local/go/src/net/http/server.go:1991 +0x607
created by net/http.(*Server).Serve
        /usr/local/go/src/net/http/server.go:3102 +0x4db

We recently bumped the version of

<http://sigs.k8s.io/controller-runtime|sigs.k8s.io/controller-runtime>

which included a breaking change made in https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.15.0. Expected behavior Secret injection works. 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

#4507 Remove deprecated InjectDecoder Pull request opened by EngHabu Tracking issue #4508 Describe your changes Controller Runtime deprecated (and completely removed) the dependency injection framework it used to have (review breaking changes section here: https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.15.0). Unfortunately this breaks very silently. InjectDecoder() is the only place as far as I can tell where we rely on that functionality. When decoders are not injected, the secrets webhook fails to parse out Pods to inject secrets too. Check all the applicable boxes ☑︎ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. Screenshots Before: image After: image Note to reviewers Related PRs PR that upgraded Controller Runtime to the breaking version: https://github.com/flyteorg/flyte/pull/4273/files flyteorg/flyte Codecov: 28.57% of diff hit (target 59.39%) ✅ 29 other checks have passed 29/30 successful checks

1 new commit pushed to

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

by EngHabu

<https://github.com/flyteorg/flyte/commit/05418513ae140ed69c55842634956c650f4ac6ea|05418513>

- Remove deprecated InjectDecoder (#4507) flyteorg/flyte

#4509 Fix $HOME resolution and webhook namespace Pull request opened by EngHabu Tracking issue Describe your changes ☑︎ Automatically resolve

$HOME

references in the config file. ☑︎ Fix the webhook configuration namespace to use

POD_NAMESPACE

downstream API Check all the applicable boxes ☑︎ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. flyteorg/flyte GitHub Actions: build-and-push-sandbox-bundled-image Codecov: 59.36% (-0.04%) compared to 0541851 Codecov: 20.00% of diff hit (target 59.40%) ✅ 27 other checks have passed 27/30 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flyte/commit/64f097fe0e80cdf44250e04ca861038d5012d845|64f097fe>

- Fix /Users/haytham resolution and webhook namespace (#4509) flyteorg/flyte

#4510 Add note on updating sandbox cluster configuration Pull request opened by jeevb Describe your changes Adds notes on updating and reloading Flyte sandbox cluster configuration. Check all the applicable boxes ☑︎ I updated the documentation accordingly. ☐ All new and existing tests passed. ☐ All commits are signed-off. flyteorg/flyte ✅ All checks have passed 30/30 successful checks

1 new commit pushed to

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

by jeevb

<https://github.com/flyteorg/flyte/commit/a8f4904353634b34a435402766bdca5d6d7a76b8|a8f49043>

- Add note on updating sandbox cluster configuration (#4510) flyteorg/flyte

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/a34ab93532f32a5c28ff65f72a7a7212e986e77c|a34ab935>

- Add

Why, What, Tests Sections

in PR Template (#2003) flyteorg/flytekit

#4511 [WIP] Agent Servicer Pull request opened by Future-Outlier Tracking issue Docs link Describe your changes Check all the applicable boxes ☐ I updated the documentation accordingly. ☐ All new and existing tests passed. ☐ All commits are signed-off. Setup Process Screenshots Note to reviewers Related PRs flyteorg/flyte WIP: Title contains "WIP" ✅ 1 other check has passed 1/2 successful checks

#4512 Add New PR Template Pull request opened by Future-Outlier As title. related PR: flyteorg/flytekit#2003 flyteorg/flyte Codecov: 59.40% (-0.07%) compared to a8f4904 ✅ 29 other checks have passed 29/30 successful checks

#4513 [Docs] move aws scheduler docs to the legacy section Issue created by samhita-alla Description delete documentation related to AWS scheduler configuration, as the flyte native scheduler should just work. reference slack thread: https://discuss.flyte.org/t/15852550/hi-team-i-have-created-a-simple-test-flyte-scheduler-using-b#929e7edd-c801-4dbb-bdbf-61cb36903727 Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#4514 [Docs] document map task parallelism constraints Issue created by samhita-alla Description map tasks generally cannot exceed the 5k limit. more info present in the slack thread. the map task docs needs to be updated. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#4515 [BUG] Failed with running tensorflow plugin in array node map task. Issue created by chaohengstudent Describe the bug Running

array node map task

will failed with following Error:

Workflow[flytesnacks:development:my_project.workflows.maptask_with_TFJob_v2.mnist_tensorflow_workflow] failed. 
RuntimeExecutionError: max number of system retry attempts [11/10] exhausted. 
Last known status message: failed at Node[n0]. 
RuntimeExecutionError: failed during plugin execution, caused by: failed to execute handle for plugin [tensorflow]: number of worker should be more then 0

It seems that the wrong custom data passing to tensorflow plugin. Expected behavior Pass with no error Additional context to reproduce 1. Activate demo cluster with tensorflow plugin enable. 2. pyflyte run following sample code.

from flytekit import task, workflow, ImageSpec
from flytekit.experimental import map_task
from flytekitplugins.kftensorflow import TfJob, Worker, Chief, PS, Evaluator
from typing import Optional, List

image_spec = ImageSpec(packages=["flytekit", "flytekitplugins-kftensorflow", "tensorflow"], registry="chaoheng"
                       , registry_config="/home/chaoheng/.docker/config.json")

task_config = TfJob(
    worker=Worker(replicas=1),
    chief=Chief(replicas=1),
    ps=PS(replicas=1),
    evaluator=Evaluator(replicas=1),
)


@task(task_config=task_config, container_image=image_spec)
def t3(a: int) -> int:
    return a + 1


@workflow
def wf() -> List[Optional[int]]:
    mt = map_task(t3)(a=[1, 2, 3])
    return mt

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

#2014 Fix array node serialize with corresponding plugin custom. Pull request opened by chaohengstudent Tracking issue Closes flyteorg/flyte#4515 Why are the changes needed? Have to get the corresponding custom to operate plugins with array node map task. What changes were proposed in this pull request? Inherit func

get_custom()

with

python_function_task

in

array_node_map_task.py

How was this patch tested? Testing kftensorflow with array node in sandbox. image Screenshots image Check all the applicable boxes ☐ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. Related PRs Docs link flyteorg/flytekit ✅ All checks have passed 2/2 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytekit/commit/5cc1b711889aaf178980ef3bec908f004033cdfa|5cc1b711>

- Override the container image of map task (#2011) flyteorg/flytekit

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/4b37b9d17bab09809f4ba0b0310fd50397a24d31|4b37b9d1>

- Introduce class decorator to flyin vscode for url exposure (#1994) flyteorg/flytekit

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytekit/commit/5c6802c97388c40d0431e4fc308e2ed651528952|5c6802c9>

- use original file/directory with local pyflyte run (#1957) flyteorg/flytekit

#4517 [UI Feature] Option to collapse Flyte console project sidebar Issue created by swarup-stripe Motivation: Why do you think this is important? There is currently no way to collapse the Flyte Console's project sidebar. It takes up quite a lot of space and is not relevant for all pages and might get in the way when looking at things like large project execution timelines, etc. Goal: What should the final outcome look like, ideally? A small button or option to collapse this sidebar. 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

#3405 [UI Feature] Flyte runtime metrics UI Issue created by cosmicBboy Motivation: Why do you think this is important? #3272 Goal: What should the final outcome look like, ideally? UPDATE: New There have been some changes from the original spec/comps. 1. We will no longer use color/opacity values. Instead, simply render the lines between spans. Users can hover over a span to see which

operationId

it represents. 2. We will fetch all execution spans using

depth=0

and will revisit this to better optimize performance in later versions if this feature starts gaining traction. 3. The hover tool-tip will be handled in a separate ticket. --- The following is out of date in the listed cases --- The new UI will be controlled by a toggle ("View Details") and will break up the graph into sections. The colors for these new buckets should be opacity values on black/white overlayed over the existing phase color. Crucially, these overlayed values should be consistent across events (eg, the overlay treatment applied to "plugin" durations should be the same regardless of phase) Propose: Link/Inline OR Additional context See high-level proposal here Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3274 [Core feature] Observability: benchmarking - create an objective set of benchmarks so we can see perf improvements/regressions on some different set of Flyte cluster configs Issue created by cosmicBboy Motivation: Why do you think this is important? Blocked by: #3272, #3273 [to be filled out] Goal: What should the final outcome look like, ideally? [to be filled out] Describe alternatives you've considered [to be filled out] 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

#4518 Remove broken link from Understand How Flyte Handles Data page Pull request opened by neverett Docs link Changed docs link: https://flyte--4518.org.readthedocs.build/en/4518/concepts/data_management.html#bringing-in-your-own-datastores-for-raw-data I removed the link from "data persistence layer". Describe your changes Removes broken link from "Bringing in Your Own Datastores for Raw Data" section of "Understand How Flyte Handles Data" docs page. Check all the applicable boxes ☐ All new and existing tests passed. ☑︎ All commits are signed-off. flyteorg/flyte Codecov: 59.40% (-0.07%) compared to a8f4904 ✅ 29 other checks have passed 29/30 successful checks

1 new commit pushed to

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

by Future-Outlier

<https://github.com/flyteorg/flyte/commit/ebed2a658dc9743d44d1601dcdbbeac762072eba|ebed2a65>

- add template (#4512) flyteorg/flyte

#4519 Bump version of goreleaser gh action to v5 Pull request opened by eapolinario Describe your changes We introduced a way to skip certain tags in #4497 but in order to use that we need a newer version of goreleaser/goreleaser-action@v5 Check all the applicable boxes ☐ I updated the documentation accordingly. ☐ All new and existing tests passed. ☐ All commits are signed-off. Setup Process Screenshots Note to reviewers Related PRs flyteorg/flyte Codecov: 59.38% (-0.08%) compared to a8f4904 ✅ 29 other checks have passed 29/30 successful checks

#1314 Initialize FlyIn Plugin Documentation Pull request opened by ByronHsu TBD flyteorg/flytesnacks GitHub Actions: Mark github pre-release as Release GitHub Actions: Publish artifacts to github release GitHub Actions: Create Prerelease GitHub Actions: Bump Version GitHub Actions: Serialize & Register Flytesnacks workflow / Register example to sandbox ✅ 25 other checks have passed 25/30 successful checks

#2016 [Enhance] Enhance code server installation based on system architecture Pull request opened by jasonlai1218 Tracking issue Why are the changes needed? These changes are necessary to increase the flexibility of the get_code_server_info function in selecting the appropriate code server based on different system architectures, including commonly used AMD64/ARM64 architectures. What changes were proposed in this pull request? • Modify `flytekit-flyin/flytekitplugins/flyin/__init__.py`: • Replace

DEFAULT_CODE_SERVER_DIR_NAME

with

DEFAULT_CODE_SERVER_DIR_NAMES

• Replace

DEFAULT_CODE_SERVER_REMOTE_PATH

with

DEFAULT_CODE_SERVER_REMOTE_PATHS

• Modify `flytekit-flyin/flytekitplugins/flyin/vscode_lib/config.py`: • Replace

code_server_dir_name

with

code_server_dir_names

• Replace

code_server_remote_path

with

code_server_remote_paths

• Modify `flytekit-flyin/flytekitplugins/flyin/vscode_lib/constants.py`: • Replace

DEFAULT_CODE_SERVER_REMOTE_PATH

with

DEFAULT_CODE_SERVER_REMOTE_PATHS

• Replace

DEFAULT_CODE_SERVER_DIR_NAME

with

DEFAULT_CODE_SERVER_DIR_NAMES

• Modify `flytekit-flyin/flytekitplugins/flyin/vscode_lib/decorator.py`: • Add

get_code_server_info

function • Replace

config.code_server_remote_path

with

code_server_remote_path

• Replace

config.code_server_dir_name

with

code_server_dir_name

How was this patch tested? • Modify

test_flyin_plugin.py

in the

plugins/flytekit-flyin/tests

directory • Add

DEFAULT_CODE_SERVER_DIR_NAMES

and

DEFAULT_CODE_SERVER_REMOTE_PATHS

to the

flytekit-flyin

plugin configuration • Add

mock_code_server_info_dict

function in the

plugins/flytekit-flyin/tests/test_flyin_plugin.py

• Add

test_arm_platform

function in the

plugins/flytekit-flyin/tests/test_flyin_plugin.py

• Add

test_amd_platform

function in the

plugins/flytekit-flyin/tests/test_flyin_plugin.py

• Add

test_platform_unsupported

function in the

plugins/flytekit-flyin/tests/test_flyin_plugin.py

Setup process Screenshots Check all the applicable boxes ☐ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. Related PRs Docs link flyteorg/flytekit ✅ All checks have passed 2/2 successful checks

#4520 [Core feature] add support for macros when using the `pyflyte register` command Issue created by samhita-alla Motivation: Why do you think this is important? currently,

flytectl register

supports the usage of macros like

{{ registration.project }}

in the python code, whereas

pyflyte register

does not. this capability can be particularly helpful when working with reference tasks or launch plans. Goal: What should the final outcome look like, ideally?

pyflyte register

needs to support macros. Describe alternatives you've considered the current workaround is to use

flytectl register

. 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