Hi! Is there a way we can store some metadata when

flytectl register file

? e.g. some k-v pairs like env vars. The intention of this is we build image containers for the workflow code, and we have to store some env vars and use this data when running the workflow. However we cannot populate them when we build the image. Currently we put them in version_id, I wonder is there a better way to do so? Thanks!

could you add env to task decorator?

@task(
    environment={"FLYTE_INTERNAL_IMAGE": "pingsutw/flytekit:0.16.0"}
)
def t1():
    ...

also labels

@freezing-airport-6809 I found an example of labels, but can we explicitly add this in the workflow annotation? We don't control this part of code, we can only control the annotation

you can create a LP with labels. https://github.com/flyteorg/flytekit/blob/90324e07f06da2fc82bc52f5db2442411fcdf42f/flytekit/core/launch_plan.py#L322

🐞 Create a new Flyte Bug issue: https://github.com/flyteorg/flyte/issues/new?assignees=&labels=bug%2Cuntriaged&template=bug_report.yaml&title=%5BBUG%5D+

we’ll add that

We are the platform team to provide Flyte to our internal users, so we cannot require users to add the LP piece of code. All our workflows are implemented as the example. If we can inject env vars from the @workflow or from the workflow registration, that would be awesome.