-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(GH-2549) Use new default modulepath #2587
Merged
Merged
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
beechtom
force-pushed
the
2549/modulepath
branch
2 times, most recently
from
January 28, 2021 18:41
558f6e0
to
60594f3
Compare
beechtom
force-pushed
the
2549/modulepath
branch
from
January 28, 2021 20:39
60594f3
to
af0872c
Compare
QQ: Does this update the generated reference docs (like bolt_project_reference) with the new defaults? When I checked this branch out and ran the rake task, I still got:
But I might be doing it wrong 😊 |
beechtom
force-pushed
the
2549/modulepath
branch
from
January 28, 2021 22:02
af0872c
to
44c5c2d
Compare
Ah, nope, forgot to update the default. Good catch! 👍 |
lucywyman
reviewed
Jan 28, 2021
lucywyman
reviewed
Jan 28, 2021
This updates Bolt to use the new default modulepath `['modules']` and append the `.modules/` directory to the end of both the default modulepath and configured modulepath. !feature * **Update default modulepath** ([puppetlabs#2549](puppetlabs#2549)) Bolt's default modulepath is now `['modules']` instead of `['modules', 'site', 'site-modules']`. Bolt will also automatically append the project's `.modules/` directory to all modulepaths, whether a project uses the default modulepath or a configured modulepath.
beechtom
force-pushed
the
2549/modulepath
branch
from
January 28, 2021 23:02
44c5c2d
to
d58e528
Compare
hestonhoffman
approved these changes
Jan 28, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docs LGTM!
|
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 updates Bolt to use the new default modulepath
['modules']
andappend the
.modules/
directory to the end of both the defaultmodulepath and configured modulepath.
!feature
Update default modulepath
(#2549)
Bolt's default modulepath is now
['modules']
instead of['modules', 'site', 'site-modules']
. Bolt will also automaticallyappend the project's
.modules/
directory to all modulepaths,whether a project uses the default modulepath or a configured
modulepath.