Jira (FACT-1772) libfacter install should support other directories than /lib
Title: Message Title Enis Inan commented on FACT-1772 Re: libfacter install should support other directories than /lib Branan Riley I did some digging through the CMakeLists files of Facter, Leatherman and Cpp-Hocon. It seems like the lib install directory for Faster is set here: https://github.com/puppetlabs/facter/blob/master/lib/CMakeLists.txt#L263 ^ What is interesting is that in 3.6.x and 3.9.x, that same line is https://github.com/puppetlabs/facter/blob/3.6.x/lib/CMakeLists.txt#L255 so will the changes required in FACT-1772 only apply to the “master” branch of Facter? The LIB_SUFFIX thing comes from Leatherman, which is used in the “leatherman_install” macro: https://github.com/puppetlabs/leatherman/blob/master/cmake/leatherman.cmake.in#L81-L91 (and here is where Facter uses it): https://github.com/puppetlabs/facter/blob/master/lib/CMakeLists.txt#L356 (for libfacter) https://github.com/puppetlabs/facter/blob/master/exe/CMakeLists.txt#L39 (for executable, dunno if this matters) The changes to specify a LIB_SUFFIX were made in this commit: https://github.com/puppetlabs/leatherman/commit/448dc6c71df95a84893407a4792efcd6ae52eab1 which go all the way back to Leatherman 0.12.x. From that commit, It seems like LIB_SUFFIX, as it is currently done, needs to be manually set in CMakeCache.txt. When I set LIB_SUFFIX to “64” there, things seem to work OK — libfacter is installed to lib64 (both libfacter.so and libfacter.so.3.9.5). This is also true for the other CPP components like Leatherman and Cpp-Hocon (their libraries are also installed to lib64). It looks like there are a set of sensible defaults we can use — https://cmake.org/cmake/help/v3.0/module/GNUInstallDirs.html has them. CMAKE_INSTALL_LIBDIR gives us what we want (it is set to "lib64" on a Fedora 26 VM). If we switch to specifying our lib directory as CMAKE_INSTALL_LIBDIR, it would require quite a bit of changes. I think a sensible solution would be to strip out the "lib" part in CMAKE_INSTALL_LIBDIR and use that as the LIB_SUFFIX. Both solutions would require an extra parameter passed into cmake so that when we build the puppet-agent, things install to the /lib directory because that is where the agent expects to find everything. Of course, better solutions are welcome. Add Comment
Jira (PUP-8461) When installing or upgrading an EXE package on Windows Puppet ignores its exit code
Title: Message Title Josh Cooper commented on PUP-8461 Re: When installing or upgrading an EXE package on Windows Puppet ignores its exit code Momtchil Momtchev Can you provide more information about what exit code install.exe is returning and why that isn't being captured correctly? For example, we currently handle reboot related exit codes 1641 and 3010. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8461) When installing or upgrading an EXE package on Windows Puppet ignores its exit code
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8461 When installing or upgrading an EXE package on Windows Puppet ignores its exit code Change By: Josh Cooper Team: Windows Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8461) When installing or upgrading an EXE package on Windows Puppet ignores its exit code
Title: Message Title Josh Cooper moved an issue Puppet / PUP-8461 When installing or upgrading an EXE package on Windows Puppet ignores its exit code Change By: Josh Cooper Affects Version/s: puppet-agent 1.10.7 Affects Version/s: PUP 4.10.7 Component/s: Windows Component/s: Windows Key: PA PUP - 1690 8461 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8460) ssh_authorized_key key update will fail on CentOS 7.4
Title: Message Title Josh Cooper moved an issue Puppet / PUP-8460 ssh_authorized_key key update will fail on CentOS 7.4 Change By: Josh Cooper Affects Version/s: puppet-agent 1.10.7 Affects Version/s: PUP 4.10.7 Key: PA PUP - 1526 8460 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (FACT-1818) zfs facts not available on linux
Title: Message Title Josh Cooper commented on FACT-1818 Re: zfs facts not available on linux We're going to be moving zfs and zpool into modules and not in core puppet. This seems like an ideal candidate for adding facts to the module instead of core facter. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8406) Puppet Error datatype uses 'message' not 'msg' as hash key
Title: Message Title Michael Smith updated an issue Puppet / PUP-8406 Puppet Error datatype uses 'message' not 'msg' as hash key Change By: Michael Smith Release Notes Summary: Part of a type that's new in 5.4. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8406) Puppet Error datatype uses 'message' not 'msg' as hash key
Title: Message Title Michael Smith commented on PUP-8406 Re: Puppet Error datatype uses 'message' not 'msg' as hash key It does not. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7884) Scheduled task test audit
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-7884 Scheduled task test audit Change By: Garrett Guillotte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8438) Pin FFI gem to 1.9.18 given current problems in FFI 1.9.21
Title: Message Title Garrett Guillotte commented on PUP-8438 Re: Pin FFI gem to 1.9.18 given current problems in FFI 1.9.21 Ethan Brown Does this need release notes? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8406) Puppet Error datatype uses 'message' not 'msg' as hash key
Title: Message Title Garrett Guillotte commented on PUP-8406 Re: Puppet Error datatype uses 'message' not 'msg' as hash key Alex Dreyer Does this need a release note for Puppet 5.4.0? Doesn't look like it. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4644) puppet tells you to read man pages that aren't installed
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4644 puppet tells you to read man pages that aren't installed Change By: Josh Cooper Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-198) Add 'bolt task show' instructions to error message for incorrect task
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-198 Add 'bolt task show' instructions to error message for incorrect task Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5494) Proper manual pages are nonexistent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5494 Proper manual pages are nonexistent Change By: Josh Cooper Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5494) Proper manual pages are nonexistent
Title: Message Title Josh Cooper commented on PUP-5494 Re: Proper manual pages are nonexistent This will be addressed in PA-1847 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-198) Add 'bolt task show' instructions to error message for incorrect task
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-198 Add 'bolt task show' instructions to error message for incorrect task Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7535) Improve man page situation and puppet --help
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7535 Improve man page situation and puppet --help Change By: Josh Cooper Fix Version/s: PUP 5.4.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7535) Improve man page situation and puppet --help
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7535 Improve man page situation and puppet --help Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8445) Deprecate "puppet man"
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8445 Deprecate "puppet man" Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 5.4.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8444) Have "puppet man" default to "--help" when run without arguments
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8444 Have "puppet man" default to "--help" when run without arguments Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 5.4.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8446) Remove "puppet man" face application
Title: Message Title Josh Cooper commented on PUP-8446 Re: Remove "puppet man" face application Moved this to the 6.0 Removals epic, so we can track all of them in one place Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Josh Cooper Team: Platform Core OS Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Josh Cooper Sprint: Platform Core Hopper OS Grooming/Triage Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1431 Pre/Post-run commands don't work under Windows Change By: Josh Cooper Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8139) Spelling Error in Error Message
Title: Message Title Josh Cooper commented on PUP-8139 Re: Spelling Error in Error Message This was fixed in 69e00c2125d3f0921d00c52054d702691d66efa6, released in puppet 4.6.0. Closing as dup Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-184) Add ability to generate Markdown
Title: Message Title Eric Putnam assigned an issue to Eric Putnam Puppet Strings / PDOC-184 Add ability to generate Markdown Change By: Eric Putnam Assignee: Eric Putnam Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title Michael Lombardi commented on PUP-8231 Re: Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp) Merged to 4.10.x at https://github.com/puppetlabs/puppet/commit/1ef5c602690c46aabe87998533bc9584a88ad19a Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-2868 `puppet config print` confusing for users Change By: Josh Cooper Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.4.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper commented on PUP-2868 Re: `puppet config print` confusing for users Commit 82b2f1189f1cd6b11814a1d468569438039028b9 causes puppet to default the section to :main (symbol), which never matches "main", so it creates a duplicate section each time. If you later use inifile to manage the file, it gets confused by duplicate sections. $ cat setconfig.sh #!/bin/sh cat < ~/.puppetlabs/etc/puppet/puppet.conf # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html # - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html [main] certname = r1nc1m63jxi6u3e.delivery.puppetlabs.net
Jira (BOLT-330) Users should be able to use wildcards to target nodes in inventory
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-330 Users should be able to use wildcards to target nodes in inventory Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5426) config set ignores --section and can insert duplicate settings if they are in [main]
Title: Message Title
Past Haus updated an issue
Puppet / PUP-5426
config set ignores --section and can insert duplicate settings if they are in [main]
Change By:
Past Haus
Comment:
We're seeing some surprising behavior in PE with this changeset in. I guess the first odd thing is that if a setting doesn't exist anywhere (and a [main] section exists), a new [main] section is added at the bottom of {{puppet.conf}}. This happens with each invocation, so after calling {{puppet config set}} 3 times, there are 4 {{[main]}} sections in {{puppet.conf}}. Starting with a puppet.conf that looks like the following:{code}# This file can be used to override the default puppet settings.# See the following links for more details on what settings are available:# - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html# - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html[main]certname = r1nc1m63jxi6u3e.delivery.puppetlabs.netserver = r1nc1m63jxi6u3e.delivery.puppetlabs.netuser = pe-puppetgroup = pe-puppetenvironment_timeout = unlimitedmodule_groups = base+pe_only[agent]graph = true[master]node_terminus = classifierstoreconfigs = truestoreconfigs_backend = puppetdbreports = puppetdbcertname = r1nc1m63jxi6u3e.delivery.puppetlabs.netalways_retry_plugins = falsedisable_i18n = true{code}I then run {{puppet config set masterport 8144}}.Now {{puppet.conf}} looks like this:{code}# This file can be used to override the default puppet settings.# See the following links for more details on what settings are available:# - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html# - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html[main]certname = r1nc1m63jxi6u3e.delivery.puppetlabs.netserver = r1nc1m63jxi6u3e.delivery.puppetlabs.netuser = pe-puppetgroup = pe-puppetenvironment_timeout = unlimitedmodule_groups = base+pe_only[agent]graph = true[master]node_terminus = classifierstoreconfigs = truestoreconfigs_backend = puppetdbreports = puppetdbcertname = r1nc1m63jxi6u3e.delivery.puppetlabs.netalways_retry_plugins = falsedisable_i18n = true[main]masterport = 8144{code}I then run {{puppet config set ca_port 8144}}.Now {{puppet.conf}} looks like:{code}# This file can be used to override the default puppet settings.# See the following links for more details on what settings are available:# - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html# - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html[main]certname = r1nc1m63jxi6u3e.delivery.puppetlabs.netserver = r1nc1m63jxi6u3e.delivery.puppetlabs.netuser = pe-puppetgroup = pe-puppetenvironment_timeout = unlimitedmodule_groups = base+pe_only[agent]graph = true[master]node_terminus =
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Past Haus commented on PUP-2868 Re: `puppet config print` confusing for users We're seeing some surprising behavior in PE possibly related to this changeset. I guess the first odd thing is that if a setting doesn't exist anywhere (and a [main] section exists), a new [main] section is added at the bottom of puppet.conf. This happens with each invocation, so after calling puppet config set 3 times, there are 4 [main] sections in puppet.conf. Starting with a puppet.conf that looks like the following: # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html # - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html [main] certname = r1nc1m63jxi6u3e.delivery.puppetlabs.net server = r1nc1m63jxi6u3e.delivery.puppetlabs.net user = pe-puppet group = pe-puppet
Jira (PUP-5426) config set ignores --section and can insert duplicate settings if they are in [main]
Title: Message Title Past Haus commented on PUP-5426 Re: config set ignores --section and can insert duplicate settings if they are in [main] We're seeing some surprising behavior in PE with this changeset in. I guess the first odd thing is that if a setting doesn't exist anywhere (and a [main] section exists), a new [main] section is added at the bottom of puppet.conf. This happens with each invocation, so after calling puppet config set 3 times, there are 4 [main] sections in puppet.conf. Starting with a puppet.conf that looks like the following: # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html # - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html [main] certname = r1nc1m63jxi6u3e.delivery.puppetlabs.net server = r1nc1m63jxi6u3e.delivery.puppetlabs.net user = pe-puppet group = pe-puppet
Jira (FACT-1819) Facter.rb is swallowing useful exception details when failing to load libfacter
Title: Message Title Ethan Brown created an issue Facter / FACT-1819 Facter.rb is swallowing useful exception details when failing to load libfacter Issue Type: Task Affects Versions: FACT 3.6.9 Assignee: Unassigned Created: 2018/02/12 2:11 PM Priority: Normal Reporter: Ethan Brown When the facter.rb shim fails to load libfacter, it raises a LoadError at https://github.com/puppetlabs/facter/blob/34e811fd856423267166981ec8f38d761cef9c17/lib/facter.rb.in#L42 However, it swallows the existing exception, including its backtrace. This information would be useful to have for debugging purposes, but is completely lost. PA-1831 is a recent case where the libfacter was not found error message has obscured vital information. Google searching also yields similar results - a handful of different problems are causing this error (for instance having locale settings incorrect). Add Comment
Jira (FACT-1819) Facter.rb is swallowing useful exception details when failing to load libfacter
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Facter / FACT-1819 Facter.rb is swallowing useful exception details when failing to load libfacter Change By: Ethan Brown Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6702) Windows service in Paused state cannot be managed
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6702 Windows service in Paused state cannot be managed Change By: Craig Gomes Team: Platform OS Windows Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1785) Add device-tree data source to libwhereami
Title: Message Title Casey Williams updated an issue Facter / FACT-1785 Add device-tree data source to libwhereami Change By: Casey Williams Fix Version/s: whereami 0.y Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1784) hypervisors fact reports false positive for LPAR/WPAR on KVM power8
Title: Message Title Casey Williams updated an issue Facter / FACT-1784 hypervisors fact reports false positive for LPAR/WPAR on KVM power8 Change By: Casey Williams Component/s: libwhereami Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1752) Add support for AIX LPAR and WPAR detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1752 Add support for AIX LPAR and WPAR detection Change By: Casey Williams Component/s: libwhereami Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1661) Add support for Solaris ldom virtualization detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1661 Add support for Solaris ldom virtualization detection Change By: Casey Williams Component/s: libwhereami Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1785) Add device-tree data source to libwhereami
Title: Message Title Casey Williams updated an issue Facter / FACT-1785 Add device-tree data source to libwhereami Change By: Casey Williams Fix Version/s: whereami 0.y Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1785) Add device-tree data source to libwhereami
Title: Message Title Casey Williams updated an issue Facter / FACT-1785 Add device-tree data source to libwhereami Change By: Casey Williams Fix Version/s: whereami 0.2.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1752) Add support for AIX LPAR and WPAR detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1752 Add support for AIX LPAR and WPAR detection Change By: Casey Williams Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1752) Add support for AIX LPAR and WPAR detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1752 Add support for AIX LPAR and WPAR detection Change By: Casey Williams Release Notes Summary: Adds functions for detecting AIX LPARs and WPARs; Relies on the output of `lparstat -i`. LPAR metdata include partition_name and partition_number. WPAR metadata includes configured_id and key. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1752) Add support for AIX LPAR and WPAR detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1752 Add support for AIX LPAR and WPAR detection Change By: Casey Williams Fix Version/s: whereami 0.2.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1661) Add support for Solaris ldom virtualization detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1661 Add support for Solaris ldom virtualization detection Change By: Casey Williams Release Notes Summary: Adds a hypervisor detection function for Solaris LDoms that is called on sparc platforms only. Relies on the virtinfo executable, and reports the following metadata if an LDom is detected:chassis_serialcontrol_domaindomain_namedomain_uuid role_control role_io role_rootrole_service => false Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1661) Add support for Solaris ldom virtualization detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1661 Add support for Solaris ldom virtualization detection Change By: Casey Williams Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1661) Add support for Solaris ldom virtualization detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1661 Add support for Solaris ldom virtualization detection Change By: Casey Williams Fix Version/s: FACT 3.y Fix Version/s: whereami 0.2.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1795) Add whereami executable
Title: Message Title Casey Williams updated an issue Facter / FACT-1795 Add whereami executable Change By: Casey Williams Fix Version/s: whereami 0.2.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8450) to_json_pretty doesn't work
Title: Message Title Joshua Knarr commented on PUP-8450 Re: to_json_pretty doesn't work You are absolutely correct. I don't recall ever having to do this before - is stdlib not included by default now? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8428) Manually smoke test all artifacts (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey commented on PUP-8428 Re: Manually smoke test all artifacts (Puppet Platform 5.4.0) Casey Williams we'll need to do this as soon as all three tagged builds are available (e.g., first thing tomorrow morning). Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8429) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8429 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13) 1. Ensure all prerequisite release tasks are complete.2. Review the release Kanban board to ensure all tickets are resolved.3. Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision.4. Send email indicating Ready To Ship milestone has been achieved. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8429) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8429 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date.2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI.3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed.4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build.5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PUP-8426) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8426 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date.2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI.3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed.4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build.5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PUP-8137) run_script function does not accept arguments
Title: Message Title Casey Williams updated an issue Puppet / PUP-8137 run_script function does not accept arguments Change By: Casey Williams Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8098) Add 'acltype' to list of supported ZFS properties
Title: Message Title Casey Williams updated an issue Puppet / PUP-8098 Add 'acltype' to list of supported ZFS properties Change By: Casey Williams Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8418) TypeError no implicit conversion of nil into String in puppet 5.3.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8418 TypeError no implicit conversion of nil into String in puppet 5.3.4 Change By: Josh Cooper Priority: Blocker Normal Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7946) Implement Puppet API for running scripts
Title: Message Title Casey Williams updated an issue Puppet / PUP-7946 Implement Puppet API for running scripts Change By: Casey Williams Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7884) Scheduled task test audit
Title: Message Title Casey Williams updated an issue Puppet / PUP-7884 Scheduled task test audit Change By: Casey Williams Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7510) FIPS-Enabled Puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7510 FIPS-Enabled Puppet Change By: Josh Cooper Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7510) FIPS-Enabled Puppet
Title: Message Title Josh Cooper commented on PUP-7510 Re: FIPS-Enabled Puppet All agent changes are done. Closing the epic. Trevor Vaughan we're looking to release 5.4.0 real soon(tm), within the week or so. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7046) Update dnf provider to support future Fedora releases
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7046 Update dnf provider to support future Fedora releases Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1967) parameter defaults of false and {} does not work
Title: Message Title
Melissa Stone commented on PUP-1967
Re: parameter defaults of false and {} does not work
I've opened up a new ticket (PUP-8442) to address the case where a parameters defaults to false. This does not handle when a user wants to default a parameter to an empty hash
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8231 Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp) Change By: Josh Cooper Fix Version/s: PUP 5.3.5 Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.4.z Fix Version/s: PUP 5.3.6 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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
Jira (BOLT-330) Users should be able to use wildcards to target nodes in inventory
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-330 Users should be able to use wildcards to target nodes in inventory Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-334) Package core task content with bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-334 Package core task content with bolt Change By: Alex Dreyer The following tasks should be packaged as part of bolt- puppetlabs-package- puppetlabs-service- puppet_conf? Tasks: - update packaging to include packages and put them on the modulepath- add documentation for modules/links to forge- add contributing section linking where to update modules. Questionsshould they be included in the gem or just the package?how should we track them(puppetfile, vanagon, git submodules) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (BOLT-334) Package core task content with bolt
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-334 Package core task content with bolt Issue Type: New Feature Assignee: Unassigned Created: 2018/02/12 10:59 AM Priority: Normal Reporter: Alex Dreyer The following tasks should be packaged as part of bolt puppetlabs-package puppetlabs-service puppet_conf? Questions should they be included in the gem or just the package? how should we track them(puppetfile, vanagon, git submodules) Add Comment
Jira (BOLT-333) Package tasks-modules content with bolt
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-333 Package tasks-modules content with bolt Issue Type: New Feature Assignee: Unassigned Created: 2018/02/12 10:54 AM Priority: Normal Reporter: Alex Dreyer We should package some core content from the task-modules control repo with bolt. tasks: 1. Move existing modules dir to bolt-modules 2. Move content from task-modules to modules 3. append modules to the modulepath 4. make modulepath an optional config value with an empty default 5. document modules 6. Add contributing section covering modules 7. make sure gem packages modules Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-255) Refactor 'nodes' into 'transport's
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-255 Refactor 'nodes' into 'transport's Change By: Michael Smith Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-321) Bolt stdlib
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-321 Bolt stdlib Change By: Alex Dreyer Epic Name: Bolt stdlib Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-321) include more content 'out of the box' in a stdlib
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-321 include more content 'out of the box' in a stdlib Change By: Alex Dreyer Team/s: Direct Change Epic Status: In Progress Epic Name: stdlib Status: Accepted Open Workflow: Scrum Team Engineering Epic Workflow Issue Type: New Feature Epic Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-321) Bolt stdlib
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-321 Bolt stdlib Change By: Alex Dreyer Summary: include more content 'out of the box' in a Bolt stdlib Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-318) I want to refer to inventory groups as targets
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-318 I want to refer to inventory groups as targets Change By: Michael Smith Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-315) Bolt Packages
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-315 Bolt Packages Change By: Lucy Wyman Bolt does not run well under ruby 2.0 which makes it hard for rh-7 users to use bolt. If we release OS packages for bolt that include or depend on ruby 2.3 this shouldn't be a problem.V1 should build packages for the linux platforms puppet-client-tools installs on. - el 7 (/) - el 6 (/) - debian 7 (/) - debian 8 (/) - sles 12 (/) - ubuntu 1404 (/) - ubuntu 1604 (/)V1 should depend on the puppet-agent package (/)V1 includes a pipeline to build the packages (/) V1 should include a plan with releng for shipping releases. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (BOLT-255) Refactor 'nodes' into 'transport's
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-255 Refactor 'nodes' into 'transport's Change By: Michael Smith Release Notes Summary: Eventually we'll document the Transport API, but not as part of this ticket. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3837) Update winston (PuppetDB 5.2.0)
Title: Message Title Russell Mull assigned an issue to Zachary Kent PuppetDB / PDB-3837 Update winston (PuppetDB 5.2.0) Change By: Russell Mull Assignee: Russell Mull Zachary Kent Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3836) Check builds, promote to PE (PuppetDB 5.2.0)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3836 Check builds, promote to PE (PuppetDB 5.2.0) Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3834) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.0)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3834 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.0) Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3835) Bump versions, push directly, and tag (PuppetDB 5.2.0)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3835 Bump versions, push directly, and tag (PuppetDB 5.2.0) Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3833) Merge-up, branch, and create pipelines (PuppetDB 5.2.0)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3833 Merge-up, branch, and create pipelines (PuppetDB 5.2.0) Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3829) (maint) Test default, not HEAD when PUPPETSERVER_VERSION unset
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3829 (maint) Test default, not HEAD when PUPPETSERVER_VERSION unset Change By: Russell Mull Fix Version/s: PDB 5.2.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8454) Prepare release announcement (Puppet Platform 5.3.5)
Title: Message Title Molly Waggett assigned an issue to Garrett Guillotte Puppet / PUP-8454 Prepare release announcement (Puppet Platform 5.3.5) Change By: Molly Waggett Assignee: Eric Sorenson Garrett Guillotte Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8459) ENC acceptance tests didn't catch regression
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8459
ENC acceptance tests didn't catch regression
Change By:
Josh Cooper
*Puppet Version:* 5.3.x*Puppet Server Version:* 5.1.xWe have various beaker acceptance tests to ensure agent and server-specified environments work as expected. Unfortunately they did not catch the regression introduced by PUP-8225 and fixed in PUP-8419. The reason is because the tests only verify that the agent eventually converges on the right environment, but doesn't test that the agent's initial node request succeeds and starts the agent off in the correct environment.For example, the following test only verifies that the notify resource emits the correct environment, but the agent's not request should not have failed, and it shouldn't have had to switch environments based on the catalog's environment:{noformat}17:23:17 Begin ruby/puppet/acceptance/tests/environment/use_enc_environment.rb...17:23:44 u0nh9955a5qfx91.delivery.puppetlabs.net (redhat6-64-2) 01:23:44$ puppet agent --no-daemonize --onetime --server cuzrxlwd8pszvvb.delivery.puppetlabs.net --verbose17:23:44 Warning: Unable to fetch my node definition, but the agent run will continue:17:23:46 Warning: Could not intern from application/json: Could not find a directory environment named 'special' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?17:23:46 Info: Retrieving pluginfacts17:23:46 Info: Retrieving plugin17:23:46 Info: Retrieving locales17:23:46 Info: Caching catalog for u0nh9955a5qfx91.delivery.puppetlabs.net17:23:46 Notice: Local environment: 'production' doesn't match server specified environment 'special', restarting agent run with environment 'special'17:23:46 Info: Retrieving pluginfacts17:23:46 Info: Retrieving plugin17:23:46 Info: Retrieving locales17:23:46 Info: Caching catalog for u0nh9955a5qfx91.delivery.puppetlabs.net17:23:47 Info: Applying configuration version '1517448226'17:23:47 Notice: expected_string17:23:47 Notice: /Stage[main]/Main/Notify[expected_string]/message: defined 'message' as 'expected_string'17:23:47 Notice: Applied catalog in 0.02 seconds{noformat} We also need to test that setting {{server_list}} also works (since we make a node request to see if the server is available).
Jira (PUP-8459) ENC acceptance tests didn't catch regression
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8459 ENC acceptance tests didn't catch regression Change By: Josh Cooper Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8459) ENC acceptance tests didn't catch regression
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8459 ENC acceptance tests didn't catch regression Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8459) ENC acceptance tests didn't catch regression
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8459 ENC acceptance tests didn't catch regression Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8459) ENC acceptance tests didn't catch regression
Title: Message Title Josh Cooper created an issue Puppet / PUP-8459 ENC acceptance tests didn't catch regression Issue Type: Bug Assignee: Unassigned Created: 2018/02/12 10:02 AM Priority: Normal Reporter: Josh Cooper Puppet Version: 5.3.x Puppet Server Version: 5.1.x We have various beaker acceptance tests to ensure agent and server-specified environments work as expected. Unfortunately they did not catch the regression introduced by PUP-8225 and fixed in PUP-8419. The reason is because the tests only verify that the agent eventually converges on the right environment, but doesn't test that the agent's initial node request succeeds and starts the agent off in the correct environment. For example, the following test only verifies that the notify resource emits the correct environment, but the agent's not request should not have failed, and it shouldn't have had to switch environments based on the catalog's environment: 17:23:17 Begin ruby/puppet/acceptance/tests/environment/use_enc_environment.rb ... 17:23:44 u0nh9955a5qfx91.delivery.puppetlabs.net (redhat6-64-2) 01:23:44$ puppet agent --no-daemonize --onetime --server cuzrxlwd8pszvvb.delivery.puppetlabs.net --verbose 17:23:44 Warning: Unable to fetch my node
Jira (PUP-8459) ENC acceptance tests didn't catch regression
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8459 ENC acceptance tests didn't catch regression Change By: Josh Cooper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8459) ENC acceptance tests didn't catch regression
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8459 ENC acceptance tests didn't catch regression Change By: Josh Cooper Fix Version/s: PUP 5.4.z Fix Version/s: PUP 5.5.0 Fix Version/s: PUP 5.3.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-321) include more content 'out of the box' in a stdlib
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-321
include more content 'out of the box' in a stdlib
Change By:
Alex Dreyer
Bolt is very powerful but users cannot access that power without writing quite a bit of puppet and ruby code or finding and installing modules.Types of content: Stdlib like puppet utility functions(puppetlabs-stdlib doesn't support bolt like -merge-, join, empty, trim ) Utility control flow plans for common paths like aggregate results, canary and batch execution Task specific functions to retry until, sleep etc. Core tasks to manage services install packages, collect facts etc Decisions:This library should consist of multiple modules that ship with bolt and Stdlib modules are appended to the module path and live in the {{modules}} directory of the bolt repo Boltlib modules should remain at the front of the module path only these functions should directly access bolt executor or inventory objects. These live in the {{???}} directory of the bolt repo For now these modules should live in the bolt repo modulepath should not be a required parameter it should be empty. Questions:How do we deal with modules that are already separate repos? Submodules? Puppetfile? vanagon? probably puppetfile perhaps backed by json. Initial modules:String: with strip and split functionsHash: with merge function???
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8443 Topscope 'environment' can become nil when setting node parameters in a custom terminus Change By: Jacob Helwig Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8443 Topscope 'environment' can become nil when setting node parameters in a custom terminus Change By: Jacob Helwig Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8443 Topscope 'environment' can become nil when setting node parameters in a custom terminus Change By: Jacob Helwig Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Jacob Helwig assigned an issue to Jacob Helwig Puppet / PUP-8443 Topscope 'environment' can become nil when setting node parameters in a custom terminus Change By: Jacob Helwig Assignee: Jacob Helwig Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8439) Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8439 Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit Change By: Josh Cooper Fix Version/s: PUP 5.4.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7046) Update dnf provider to support future Fedora releases
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7046 Update dnf provider to support future Fedora releases Change By: Kenn Hussey Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8458) Communicate scope and timeline of next release (Puppet Platform 5.3.5)
Title: Message Title Molly Waggett created an issue Puppet / PUP-8458 Communicate scope and timeline of next release (Puppet Platform 5.3.5) Issue Type: Task Assignee: Kenn Hussey Created: 2018/02/12 9:45 AM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-15) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8457) Update Confluence and JIRA based on release (Puppet Platform 5.3.5)
Title: Message Title Molly Waggett created an issue Puppet / PUP-8457 Update Confluence and JIRA based on release (Puppet Platform 5.3.5) Issue Type: Task Assignee: Kenn Hussey Created: 2018/02/12 9:45 AM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-15) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8456) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.3.5)
Title: Message Title Molly Waggett created an issue Puppet / PUP-8456 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.3.5) Issue Type: Task Assignee: Kenn Hussey Created: 2018/02/12 9:44 AM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-15) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
