Hi Gael, This sounds interesting, but I couldn’t find the PR. Could you link to it?
Cheers, Jim On 28/06/2017, 22:08, "Gael Magnan" <[email protected]> wrote: >Hi, > >A few months ago I started working on a refactoring of the connections so >it would be easier to add new types. It never got merged but you probably >can find it still in the pr liste. > >I think a complete overhaul of the connections is more than needed. >Especially removing the default ones and the hard coded types. > >Regards >Gael > >Le mer. 28 juin 2017 à 21:39, David Capwell <[email protected]> a écrit : > >> Thanks! Yeah, using http type for now and things are working just fine >> >> On Jun 28, 2017 12:17 PM, "Rutherford, James" < >> [email protected]> wrote: >> >> > Hi David, >> > >> > I’m also a bit of an Airflow novice but what I’ve figured out is that >> > Connections are essentially parameters for Hooks. The connection type >> > doesn't seem to be used for anything explicitly (the list of choices is >> > hard-coded in the Airflow source). >> > >> > For example, I made a SharePoint hook that defines how content goes into >> > and comes out of SharePoint. The connection information (URL, protocol, >> > credentials, etc) is stored as a Connection with type set as 'Samba' (it >> > was the closest I could find); the Hook just wraps the SharePoint API. >> > >> > >> > I hope that helps. >> > >> > Cheers, >> > >> > Jim >> > >> > >> > >> > On 28/06/2017, 19:05, "David Capwell" <[email protected]> wrote: >> > >> > >I'm just starting out with airflow and looking to add my own artifactory >> > >hook so my tasks can pull from there. >> > > >> > >Looking at the docs this means I need a ArtifactoryHook but not clear to >> > me >> > >how this integrates with connections. Looking over the connection code >> > the >> > >mapping is hard coded but the plug-in docs say to just build a hook. I >> > >have a hello world hook but not sure how to link it with connections >> > >(connection tab does not list it) >> > > >> > >Thanks for your time reading this email >> > >> > ________________________________ >> > >> > This email is intended solely for the recipient. It may contain >> > privileged, proprietary or confidential information or material. If you >> are >> > not the intended recipient, please delete this email and any attachments >> > and notify the sender of the error. >> > >> ________________________________ This email is intended solely for the recipient. It may contain privileged, proprietary or confidential information or material. If you are not the intended recipient, please delete this email and any attachments and notify the sender of the error.
