Jira (PUP-8553) PAL should be able to run with 'empty' puppet settings

Alex Dreyer (JIRA) Thu, 15 Mar 2018 15:04:19 -0700

Title: Message Title

Alex Dreyer created an issue

Issue Type:	New Feature
Assignee:	Unassigned
Created:	2018/03/15 3:03 PM
Priority:	Normal
Reporter:	Alex Dreyer

Problem:
When using PAL puppet settings may be unexpectedly be picked up from puppet's configuration directories.

Bolt has hacked around this problem by wrapping PAL calls with:

    def with_puppet_settings

      Dir.mktmpdir('bolt') do |dir|

        cli = []

        Puppet::Settings::REQUIRED_APP_SETTINGS.each do |setting|

          cli << "--#{setting}" << dir

end

        Puppet.settings.send(:clear_everything_for_tests)

        Puppet.initialize_settings(opts)

        yield

end

end

Since PAL usage is likely to be separate from puppet's existing configuration this seems like a problem that should be solved in PAL itself. I'm not sure generally how PAL users want to interact with system puppet settings, if they need to initialize them in a non-empty state, reinitialize them, or are concerned with the global statefulness of them.

For bolt's current usage a method to initialize empty puppet settings once for the duration of the process would be adequate.

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8553) PAL should be able to run with 'empty' puppet settings

Reply via email to