Skip to content
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

(maint) Debug output GEM_HOME and GEM_PATH before executing module commands #268

Merged
merged 1 commit into from
Aug 25, 2017

Conversation

james-stocks
Copy link

To aid troubleshooting in cases of ruby environment doubts.

@@ -217,6 +217,9 @@ def run_process_in_clean_env!
def run_process!
command_string = argv.join(' ')
PDK.logger.debug(_("Executing '%{command}'") % { command: command_string })
if context == :module
PDK.logger.debug(_("GEM_HOME is '%{gem_home}' and GEM_PATH is '%{gem_path}'") % { gem_home: @process.environment['GEM_HOME'], gem_path: @process.environment['GEM_PATH'] })
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm this should perhaps specify that these are the environment values for the command process

@coveralls
Copy link

Coverage Status

Coverage increased (+0.008%) to 93.683% when pulling 378512d on james-stocks:log_gem_env into d02f959 on puppetlabs:master.

…mmands

To aid troubleshooting in cases of ruby environment doubts.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.008%) to 93.683% when pulling 6e2cb5a on james-stocks:log_gem_env into d02f959 on puppetlabs:master.

@DavidS DavidS merged commit bafb86f into puppetlabs:master Aug 25, 2017
@DavidS DavidS deleted the log_gem_env branch August 25, 2017 08:19
@DavidS DavidS added the feature label Sep 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants