Wow, you've got a lot of points there!
1. Deployment Names vs. Unique Flow Names:
Your team’s wondering why deployment names are needed at all when making the flow name unique could suffice. It's true, on the surface, giving each flow a unique name could solve organizational headaches. But deployment names are more about the flexibility to have multiple deployable configurations for the same flow.
2. UI Grouping Issues:
Yep, if the deployments aren’t grouping properly in the UI, it can feel like the deployment names are pointless. Relying on deployment names without UI backup can be frustrating.
3. Version Parameter:
Ouch. It hurts when a feature exists but doesn’t actually do anything. That’s super annoying, especially if you're expecting it to manage different versions of your deployment accurately.
4. No DAG Generation:
Prefect not generating DAGs (like Airflow does) can be another bummer, given it's easier to visualize and manage complex workflows with subflows this way.
To wrap this up:
1. Prefect requires deployment names for the backend configuration, but it might be overkill for simple use cases.
2. The UI might not reflect the organizational layer you'd expect.
3. Version parameters sitting idle feels like a draft feature.
Let’s look into issues and discussions related to these points on GitHub to see if there are ongoing fixes or workarounds. I'll check for relevant issues and updates from the Prefect GitHub repo to try and get some clarity or helpful solutions. Hang tight.
Alright, let's break this down based on current info and GitHub issues:
1. Deployment Names & UI Grouping:
- Prefect requires deployment names for organizational purposes. Complaints about how they are displayed in the UI are valid.
-
Issue: Add option to Archive or hide deployments implies efforts are being made to improve deployment visibility.
-
Improved Filtering: Improved search and filter in Prefect UI is another step towards better dashboard management.
2. Version Parameters:
- The usability of version parameters is questioned.
-
Issue: Deployment versioning suggests a need for better version management and display in UI.
3. No DAG Generation for Flows/Subflows:
- Prefect’s current handling of tasks included in lists complicates DAG visualization.
-
Issue: Phantom `List` task complicating the DAG underlines that Prefect does generate some elements for the DAG, although imperfectly.
Based on all this, Prefect is likely working on improvements but hasn't solved all concerns yet. If the specifics are crucial for your workflow, these GitHub issues are the place to track progress or even contribute feedback for faster resolutions.
For full context:
-
Add option to Archive or hide deployments
-
Improved search and filter in Prefect UI
-
Deployment versioning
-
Phantom `List` task complicating the DAG
Hope this helps!