GitHub user mdedetrich edited a discussion: Split out google connectors into its own repo
So due to the fact that I have started working on google cloud storage and there will be feature/behaviour changes which asks for a 1.2.x release I was wondering whether it makes sense to start our journey on splitting out various connectors from this pekko-connectors mono repo and that we can start with google cloud storage. Specifically with google cloud storage, I was thinking that we should actually have 2 repos. One which stores google-common (for those who don't know, google common has all of the shared code for all of the other google related connectors, primarily auth related) and then we would have another repo for each other google component, i.e. google-cloud-storage, google-bigquery etc etc. Just to be clear, this would be primarily moving code around. There won't be any breaking binary changes (which can be confirmed with MiMa) and all artifact names etc etc would remain the same wdyt? GitHub link: https://github.com/apache/pekko-connectors/discussions/1034 ---- This is an automatically sent email for notifications@pekko.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@pekko.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
