Add RequiredHostSpec #146
Merged
Add RequiredHostSpec #146
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
We want to gracefully handle the case where there's no booted/staged image - i.e. when there's no spec. However we only support deploying a container image. So add a `RequiredHostSpec` that is like `HostSpec` but without the `Option`. This drops out a few unnecessary `Option`-juggling in the deploy code. Prep for adding configmaps to the spec. Signed-off-by: Colin Walters <walters@verbum.org>
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.
We want to gracefully handle the case where there's no booted/staged image - i.e. when there's no spec.
However we only support deploying a container image. So add a
RequiredHostSpecthat is likeHostSpecbut without theOption.This drops out a few unnecessary
Option-juggling in the deploy code.Prep for adding configmaps to the spec.