include blueprint import file option #347
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
luisarizmendi
requested review from
maxamillion,
thom-at-redhat,
de1987,
resoluteCoder and
matoval
as code owners
|
This Pull Request looks stale. Feel free to reopen it if you think it's a mistake. |
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.
Description
This is the first approach to cover [1]. I didn't modify any module, I just added a new
builder_blueprint_import_filevariable. If the variable is defined, then it copies the file into the image builder, and then pushes that blueprint instead of creating the blueprint from the vars.[1] #225
Type of change
What is it?
Checklist