Accept path to OSIE tar as env for tinkerbell setup #140
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.
As the
setup.sh
executes, it downloads the latest of Osie. This will not efficient for local setup with Vagrant, as you may have to destroy your provisioner VM for various reasons.The setup script will first read the
TB_OSIE_TAR
variable. If it is set, the setup will skip the download and extract the file providedtar
instead. If not, it will go ahead and download the latest of Osie.For your Vagrant setup, you can download the tar and then sync the containing directory with the provisioner VM. Now, set the environment variable to the synced folder. For instance:
Signed-off-by: Gaurav Gahlot [email protected]