Hello! I noticed that we are able to set tags on task's decorators and when defining a deployment but not on flow decorators. There is always the

with tags("test"):

option but still this applies to tasks inside a flow. Is this a design choice? There are some use cases where setting tags for flows could be proved useful for me

Hello Andreas! Could you elaborate more on the use cases you are mentioning?

The 1st one would be to be able to categorize them and filter them easily like in deployments using keywords. The 2nd one would be when trying to create deployments from flow objects using the the

Deployment

Python object (instead of the cli). I want to provide the tags there for creation and fetch them dynamically from the flow object without the need to store them manually somewhere else. For example the flow object includes the name and the desctiption which is now fetched automatically when we create the deployment

Hi Andreas, thank you for the explanation. I'd recommend opening a feature request describing what you have mentioned here.