Did the default service account with which launch ...
# contribute
c
Did the default service account with which launch plans are registered change to
"demo"
going from flytekit 1.12 to 1.13? We have a custom registration/launch script which sets
options = Options.default_from(k8s_service_account="", raw_data_prefix="")
and suddenly see executions with a non-existing
"demo"
sa. Fixed by explicitly configuring the
"default"
account but I wonder where this changed - but in a quick search I couldn’t find where. 🤔
f
Ohh what, that’s not intentional
Can you share a PR?
Cc @high-accountant-32689
c
I don’t know where
"demo"
is set unfortunately
I just explicitly hard code it to
"default"
again in our registration script.
h
This is weird. Let me see what I can find.
🙏 1
c
Thank you 🙏 For us it’s not a problem so no pressure, was just meant as a headsup
h
Yeah, I'm not sure. Can you give more details about those launch plans? Are they cron schedules? Can you get to the call to
create
or
get_or_create
in your script and double check what's being passed there?
c
Copy code
from flytekit import task, workflow

@task
def foo():
    ...


@workflow
def my_wf():
    foo()
This simple example is enough for me but I do see it now with flytekit 1.12 or 11 so I think this is something on my side even though I don’t understand it at this point. Please excuse the false alarm 🙇
h
no worries. Let us know how we can help.