search

alphagov / paas-cf-conduit

MIT License
20 stars 10 forks source link

Combine efforts? #24

Open afeld opened 6 years ago

afeld commented 6 years ago

Hello! I'm at @18F, and one of the authors of Service Connection Plugin. I was just going to submit the plugin to the Cloud Foundry Plugin Directory, and came across yours. It seems like the two projects have the same goal - any interest in combining forces on them?

afeld commented 6 years ago

Bump!

chrisfarms commented 6 years ago

Hi @afeld... Sorry we have neglected this issue!

We'd definitely be open to sharing the load and welcome contributions... do you have any ideas of what "combining forces" might look like? Are there features you would be pushing for?

There are a few things in conduit currently that are somewhat specific to our platform's brokers (see https://github.com/alphagov/paas-cf-conduit/issues/13) ... but nothing that could not be resolved by making it a bit more intelligent at detecting common client commands, service names and binding credential formats.

I personally like the idea proposed in https://github.com/18F/cf-service-connect/issues/18 (or something similar to it) that could allow the plugin to work even for cases where some kind of heruistic detection of service/client/credentials fails.

afeld commented 6 years ago

We (@18F / cloud.gov) would be fine deprecating cf-service-connect in favor of conduit if conduit had feature parity. (I haven't checked.) The main thing would be making sure it supports our brokers. I guess a start would be trying to copy the tests in and see how far we get?