Runtime Interface #20
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add more details about each build plan step in a simplified form
sketch out an interface in pseud-go code for an Execute func
these are definitely just rough suggestions!
|
Closing this one out - looks like a useful document to reference in the future but the conversation (and people 😢) has moved on at this point. The K8s experiment was pretty fruitful and we'll be working on a proper runtime some time this year. 🎉 |
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposal
This RFC serves to split the discussion in #2; driving toward a clear interface of what is expected of the "Runtime". Hopefully this brings forth a more actionable path to implementing new engines for the runtime, and serves as a discussion point around boundaries of what's currently considered the "Runtime"