• Mark McDonald

    Mark McDonald

    2 years ago
    Hi - I'm working on a flow wherein I have a task that I only want to run when a particular upstream task fails. I've read through the docs and I am trying to use triggers to do this. There are a lot of flavors of triggers: all_finished, all_successful, all_failed, any_successful, any_failed, some_failed, etc. However, it's not clear to me if there is a way to specify if one particular upstream task failed to trigger the downstream task. I don't want to use some_failed or any_failed because there is a good chance that the failure happened at a task elsewhere in the flow
    Mark McDonald
    Chris White
    3 replies
    Copy to Clipboard
  • Braun Reyes

    Braun Reyes

    2 years ago
    is it possible to trigger a task based on the value of parameter? like...
    @task(trigger=<boolean based off value of parameter)
    Braun Reyes
    Chris White
    6 replies
    Copy to Clipboard
  • Braun Reyes

    Braun Reyes

    2 years ago
    trying to tie the triggering of certain tasks based on different schedules
  • Braun Reyes

    Braun Reyes

    2 years ago
    different clocks that is since we can pass default parameters per schedule
  • a

    Amit Singh

    2 years ago
    @here is there a way to send html emails using prefect.tasks.notifications.email_task.EmailTask
    a
    Zachary Hughes
    2 replies
    Copy to Clipboard
  • Jeff Brainerd

    Jeff Brainerd

    2 years ago
    Hey Prefect team, would like to upvote the issue to provide ability to run prefect flow container as non-root. This is definitely a problem for us.https://github.com/PrefectHQ/prefect/issues/2025 Does anyone have a workaround?
    Jeff Brainerd
    Chris White
    +1
    4 replies
    Copy to Clipboard
  • c

    Cab Maddux

    2 years ago
    Hi! When having the Kubernetes Agent trigger flows, I haven't been able to have the agent create my job with a custom k8s config yaml (it creates the job, just with the default k8s config yaml). Shouldn't I be able to use
    flow.environment = KubernetesJobEnvironment(job_spec_file='...')
    prior to
    flow.register()
    and have the k8s agent use my
    job_spec_file
    to create the job? My job spec file is basically just the example here: https://docs.prefect.io/cloud/execution/k8s_job_environment.html#examples
    c
    2 replies
    Copy to Clipboard
  • j

    John Ramirez

    2 years ago
    Hey - does anyone have a code sample for Control Flow task such as
    switch
    and
    ifelse
    j
    Zachary Hughes
    8 replies
    Copy to Clipboard
  • Scott Zelenka

    Scott Zelenka

    2 years ago
    Is it possible to make an EnvVarSecret "required" similar to how Parameters are required? https://docs.prefect.io/api/latest/tasks/secrets.html#secret
    Scott Zelenka
    1 replies
    Copy to Clipboard
  • Jeff Brainerd

    Jeff Brainerd

    2 years ago
    Hi Prefecters, I’m struggling with a peculiarity of Django, but I’m wondering if the problem is somewhat more general. The basic issue is that I need to initialize django before importing any ORM objects that many of my prefect tasks use. When Dask is running a task, I’m able to use an initialization hook to call that django function before the flow is deserialized with cloudpickle. The problem comes when building the prefect docker image -- the healthcheck fails during cloudpickle load. I’ve done some code spelunking and I can’t see an obvious way to override or provide a hook to the healthcheck script short of just hacking it (which I’m doing just to get it to pass). So I’m interested if there’s an existing workaround, or if this problem has come up before and if anyone else would benefit from some kind of mechanism for overriding, disabling or providing some kind of pre-run hook for the healthcheck script. Thanks all 🙏
    Jeff Brainerd
    Chris White
    +2
    6 replies
    Copy to Clipboard