Skip to content

Run Engine.SetAvailable() on all engines #47

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

Merged
merged 1 commit into from
Nov 7, 2016

Conversation

ctrochalakis
Copy link
Contributor

SetAvailable() was invoked only for the docker engine, since it is the
only engine that actually hooks its fetching logic there.

The side-effect was that a new engine would not have an entry point for
fetching a bundle.

SetAvailable() was invoked only for the docker engine, since it is the
only engine that actually hooks its fetching logic there.

The side-effect was that a new engine would not have an entry point for
fetching a bundle.
@kevsmith
Copy link
Member

@ctrochalakis Could you sign the CLA (available from the above details link) so we can merge your PR?

@ctrochalakis
Copy link
Contributor Author

Hello @kevsmith, I think it should be ok now.

@kevsmith kevsmith merged commit 67e6389 into operable:master Nov 7, 2016
@kevsmith
Copy link
Member

kevsmith commented Nov 7, 2016

Merged! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants