packer-rocm/os-prep: block reposync tasks, allow non-packer runs #75
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
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.
This set of Packer-specific tasks make the playbook not particularly friendly when run natively, insisting the input of 'repository overrides' exist.
Assume the repositories given to
packer-rocmshould be synchronized with the managed host... but allow it to be opted-out. Also, tag the tasks.This makes
os_prep.ymlgenerally much more useful when not building an image. For instance:cloud-init+ansible-pullwhile building a live system, no Packer involved.