Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

Start refactoring the executor to further split up Docker and runtime… #52

Merged
merged 1 commit into from
Feb 6, 2018

Conversation

sargun
Copy link
Contributor

@sargun sargun commented Feb 6, 2018

This PR should have no functional / logical changes. It's just rearranging code so runtime/executor.go can be factored out into common (stateless, and stateful) code to be shared between one-shot container run, and long-running code.

@sargun sargun requested a review from fabiokung February 6, 2018 02:28
@sargun sargun force-pushed the multi-executor branch 2 times, most recently from b24c4d5 to 3b2fba8 Compare February 6, 2018 02:47
Copy link
Contributor

@fabiokung fabiokung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, though I'm not 100% sure why moving things from runtime to runtime/types will help. Maybe that will become clearer with future patches? Will it help prevent some circular dependency?

Right now it's in an odd state where runtime is mostly empty and could probably go away (be entirely empty thus not a Go package), and there's no visible difference in having things inside types vs inside runtime.

@sargun
Copy link
Contributor Author

sargun commented Feb 6, 2018

There was common code between the independent executor path, and runtime. As I'm refactoring, I'm trying to separate out the common code vs. code that has the shared state in it.

@sargun sargun merged commit 061f4a2 into master Feb 6, 2018
@sargun sargun deleted the multi-executor branch February 6, 2018 18:31
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants