Channels
pacc-july-11-12-2023
pacc-sept-20-21-2023
pacc-aug-16-2023
pacc-aug-29-30-2023
pacc-may-31-2023
prefect-ai
pacc-sept-26-27-2023
pacc-clearcover-june-12-2023
pacc-july-6-2023
intros-test
livestream-chatter
marvin-in-the-wild
data-ecosystem
geo-israel
pacc-june-14-2023
geo-japan
pacc-london-2023
pacc-sept-13-14-2023
prefect-cloud
ppcc-may-16-2023
prefect-azure
prefect-docker
prefect-recipes
gratitude
geo-nyc
geo-bay-area
geo-boston
geo-london
geo-dc
geo-chicago
geo-berlin
geo-texas
geo-seattle
geo-colorado
pacc-july-17-18-2023
introductions
prefect-server
data-tricks-and-tips
prefect-aws
prefect-gcp
find-a-prefect-job
prefect-dbt
random
events
ask-marvin
show-us-what-you-got
prefect-getting-started
prefect-integrations
prefect-contributors
best-practices-coordination-plane
announcements
prefect-ui
prefect-kubernetes
pacc-aug-22-23-2023
prefect-community
Powered by
#prefect-community
Title
a
ale
10/05/2020, 12:18 PM
Hi folks, we’re configuring Prefect to run tasks with Fargate Agent. Is there a way to tell Prefect to create task definitions with a predefined naming convention instead of flow_name along with tags flow_id and flow_version?
j
josh
10/05/2020, 1:39 PM
Hi
@ale
currently it doesn’t appear that there is a way in the fargate agent to override this default behavior.
https://github.com/PrefectHQ/prefect/blob/7fe55a83f275a01d95268ff9e4bd5f5b349728e1/src/prefect/agent/fargate/agent.py#L478-L489
Maybe we could expose a callable that could be used to template the name if you want to open an enhancement request for it on the repo 🙂
👍 1
Post