• j

    jcozar

    6 months ago
    Hi! Has anyone tried to implement a new type of prefect agent? I would like to read more about how it works. I don’t know if Prefect Agent is always asking Prefect Server/Cloud to run new flow runs, or if Prefect Server/Cloud sends actively the flow run to an active agent. I’m thinking of a Prefect Webhook Agent that, when there is a new flow run to be executed, invoke a webhook that executes the flow run. For example, in AWS it could be API Gateway running a AWS Lambda function or Fargate task to run the flow run. Do you think it would be possible? Thank you in advance!
    j
    Anna Geller
    +1
    5 replies
    Copy to Clipboard
  • b

    Brett Naul

    6 months ago
    we might be interested in taking a stab at finishing https://github.com/PrefectHQ/prefect/pull/3664, @Michael Adkins @Chris White any more thoughts since your reviews in uh late 2020? 😬 tbh I would be happy with just
    flow_run_name={today}
    or anything along those lines, templating just seems like one way to achieve that
    b
    Michael Adkins
    2 replies
    Copy to Clipboard
  • Stéphan Taljaard

    Stéphan Taljaard

    6 months ago
    Hi. Where's
    prefect-gcp
    on your Collection roadmap? Depending on timelines, I might collaborate
    Stéphan Taljaard
    Kevin Kho
    +2
    6 replies
    Copy to Clipboard
  • Andrew Huang

    Andrew Huang

    6 months ago
    Shout out to @davzucky for the first ever PR to one of our Prefect 2.0 Collections (prefect-aws)!
  • ale

    ale

    5 months ago
    Hey folks 👋 Are there any guidelines to “convert” existing Prefect 1.0 tasks to make them work with Prefect 2.0?
    ale
    Anna Geller
    +1
    23 replies
    Copy to Clipboard
  • a

    Anders Segerberg

    5 months ago
    I'm encountering this CI issue today, I didn't have it on Friday:
    =========================== short test summary info ============================
    ERROR tests/tasks/sodaspark/test_sodaspark_tasks.py - TypeError: argument of ...
    ERROR gw2
    SKIPPED [1] tests/tasks/asana/test_asana_task.py:8: could not import 'asana': No module named 'asana'
    SKIPPED [1] tests/tasks/dbt/__init__.py:3: could not import 'dbt': No module named 'dbt'
    SKIPPED [1] tests/tasks/great_expectations/__init__.py:3: could not import 'great_expectations': cannot import name 'contextfilter' from 'jinja2' (/usr/local/lib/python3.8/site-packages/jinja2/__init__.py)
    a
    Kevin Kho
    +3
    7 replies
    Copy to Clipboard
  • ale

    ale

    5 months ago
    Hey folks, I’ve created another collection!https://alessandrolollo.github.io/prefect-transform/tasks/ cc @Rahul Sompuram
    ale
    1 replies
    Copy to Clipboard
  • a

    Anders Segerberg

    5 months ago
    Is squash-on-merge enabled?
    a
    1 replies
    Copy to Clipboard
  • ale

    ale

    5 months ago
    Hey folks 👋 A
    prefect-dbtcloud
    collection is coming soon 🔥
    ale
    Anna Geller
    9 replies
    Copy to Clipboard
  • ale

    ale

    5 months ago
    Quick question regarding the Github Action that runs when pushing a change to a Prefect collection repo: the CodeQL step takes ~30 minutes to run each time. Is this expected?
    ale
    Anna Geller
    +1
    6 replies
    Copy to Clipboard