@Marvin I am using a severless push workpool. Is there any way to make customisations to the deployment name? The full deployment name is always

prefect-{DEPLOYMENT_NAME}-{SOME-GENERATED-ID-OF-LENGTH-36}

. Without the my defined deployment name it is already 45 characters. The deployment fails if the name exceeds the length of 64 characters. This is quite annoying as keeping my deployment names to 19 characters is very limiting. Error is:

Flow run could not be submitted to infrastructure: (InvalidDeployment) The provided deployment name 'FULL_DEPLOYMENT_NAME_HERE' has a length of '77' which exceeds the maximum length of '64'. Please see <https://aka.ms/arm-deploy> for usage details.

The deployment name in Prefect is indeed a part of the full deployment name and must be unique. However, the limitation you're experiencing seems to be related to the Azure Resource Manager (ARM) which has a maximum length of 64 characters for the deployment name. This is a limitation of Azure, not Prefect. Unfortunately, there doesn't seem to be a way to customise the length of the generated ID or the prefix

prefect-

in the full deployment name. This means you'll have to keep your deployment names within the limit to avoid the error. For more details, you can refer to the following documents: - Push Work to Serverless Computing Infrastructure - Prefect Deploy Guide - Concepts: Deployments and Flows

@Marvin is there any place i can request an update to this feature. I understand it is a limitation of azure, but it is going to be hard making the flows distinguishable with only 19 characters. At least get rid of the prefect_ in the begining

There is an open issue on Prefect's GitHub repository that matches your concern. The issue, titled "Azure Container Instance Worker Creates Invalid Length ARM Deployment Names", discusses the problem of the deployment name exceeding the maximum length allowed by Azure. You can contribute to this issue by adding your comments and use case to it. This will help the Prefect team understand the impact of this issue and prioritize it accordingly. If you have a GitHub account, you can comment on the issue directly. If you don't have an account, it's easy to create one. Additionally, you can also create a new feature request if you feel that your concern is not fully covered by the existing issue. When creating a new issue, make sure to provide as much detail as possible about your use case and the problem you're facing. This will help the Prefect team understand your needs and develop a solution that fits them.