-
Notifications
You must be signed in to change notification settings - Fork 354
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
r10k deploy [environment|module] does not deploy modules #26
Comments
By default This is definitely an issue because I haven't made this distinction terribly clear in the documentation. How would you like this behavior to be displayed? Would you like to have a specific command equivalent to the old |
Ah, I see. The reason I didn't catch the -p flag was that I didn't realize that there was another level of help text at "r10k deploy environment --help", where it is nicely explained, and it works nicely. I don't require any more documentation than that. By the way, did you notice that the OPTIONS section alternates randomly between being right after the USAGE section and being last? Not really a problem, but it is surprising.
|
Well, that's really weird that those fields are flip-flopping. This will probably have to be fixed in upstream; I'll see if I can get that worked out before 1.1.0. Thanks for noting that! |
I've reported this upstream in denisdefreyne/cri#14, since this is an upstream issue I'm going to close this issue in favor of the upstream one. @larstobi thanks again for reporting this! |
…-custom-gem-path Bugfix/3.8.x/remove custom gem path
r10k deploy [environment|module] only deploys environment, but does not checkout the modules into /etc/puppetlabs/puppet/environments/master/modules. Only the Puppetfile and the other contents of the r10k-shared branch are checked out, but no action is run on the Puppetfile.
If I cd to the "/etc/puppetlabs/puppet/environments/master/" and run "r10k puppetfile install" then it will install the modules.
r10k version from git: b98b173
The text was updated successfully, but these errors were encountered: