Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider moving transports into separate gems #527

Open
stevendanna opened this issue Oct 26, 2019 · 0 comments
Open

Consider moving transports into separate gems #527

stevendanna opened this issue Oct 26, 2019 · 0 comments
Labels
Platform: GCP Type: Enhancement Improves an existing feature

Comments

@stevendanna
Copy link
Contributor

This would likely be a breaking change, but it might be nice to make the various
transports their own gems so that it was easier to opt-into functionality. Currently, depending
on train also pulls in the google-api-client gem which is 46MB on disk, a pretty hefty dependency if we aren't going to be using that transport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Platform: GCP Type: Enhancement Improves an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants