(GH-2652) Support Puppet paths in 'bolt script run' #2688
Merged
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 adds support for using Puppet paths (
<MODULE NAME>/<FILE NAME>
)in
bolt script run
andInvoke-BoltScript
. The default behavior is tostill locate the script file using an absolute/relative path, but Bolt
will now fall back to checking if the path is a Puppet path if that
fails.
!feature
Support Puppet paths when running scripts from the CLI
(#2652)
You can now use Puppet paths (
<MODULE NAME>/<FILE NAME>
) to specifythe path to a script when running
bolt script run
orInvoke-BoltScript
.