Thanks Sam I'm curious how the dag versioning features will interact with your workflow. i'm not sure that it will immediately solve all of your use case. i imagine you would probably have some good feedback on how to improve / make it more useful.
On Mon, Feb 3, 2025 at 3:04 PM Sam Wheating <samwheat...@gmail.com> wrote: > Hi Daniel, > > I can speak on behalf of Reddit Ads - we use this feature extensively in > our pre-production environment. > > In short, we create per-branch zip archives which contain all custom > operators and shared code as well as any DAGs modified in that branch. This > allows multiple developers to concurrently test different changes to the > same DAGs or operators in a shared remote airflow deployment - since all > imports are localized to the zip archive there's no interference between > different branches. > > I can provide more details if needed, but I just wanted to say that this > feature has been very useful for us. If there's a better way of providing > isolated development namespaces in a shared environment, I would love to > hear about it. > > Sam > > On Mon, Feb 3, 2025 at 11:45 AM Daniel Standish > <daniel.stand...@astronomer.io.invalid> wrote: > > > Recall, we can put dags inside of zip files and airflow will unzip and > find > > the dags. > > > > Do people actually use these? Is there still a reason to support this > > feature? > > >
