Installing plugins

[gusostow]

Is there a best practice for installing these, or all airflow plugins in general? Anything more standard to environment set up than manually copying code into the plugins folder?

I see in the airflow docs that you can distribute plugins as python packages, which seems like a good idea because then they would be pip installable, and can be released onto PyPi.

I'm interested in contributing a plugin to your org. Should I follow the current convention, or structure my plugin like a package?

[virajmparekh]

Hi @gusostow - we do not have any best practices on packing plugins in general right now.

We were meaning to contribute some of these onto PyPi or into core Airflow, but have not gotten around to it yet.

We would love for you to contribute a plugin! Please package it in whatever manner is easiest for you, be it a package or the convention we've used here!

[gusostow]

@vparekh94 thanks! Excited to share. I think you might need to add me to the airflow-plugins org for me to be able to create a new repo?

[stonecharioteer]

@virajmparekh I'm asking this here because I don't really know where else to ask this.

When making a python package that leverages airflow, and is meant to mainly be used within airflow, should airflow be added as a depedency? I'm asking this because when we do so, we lock ourselves to certain versions of airflow as opposed to allowing our code to be tested against any verison of it. I'd remove the version tagging, but is there some other pattern you'd recommend?