Jira (FACT-1828) libwhereami does not compile with gcc 7.3.0
Title: Message Title Branan Riley commented on FACT-1828 Re: libwhereami does not compile with gcc 7.3.0 That style of throw specification has been deprecated since C++11 or 14. I'm surprised the compiler we build on didn't complain about this (and I apologize for writing and/or approving the code that introduced it) I can't promise we'll get to it immediately if we have to do the work, but a pull request to remove those exception specifications would get merged pretty quickly. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1827) AIX hardwaremodel (os -> hardware) fact is non-standard
Title: Message Title Branan Riley commented on FACT-1827 Re: AIX hardwaremodel (os -> hardware) fact is non-standard Thanks for reporting this. We agree that the use of various hardware-related facts (hardware, ISA, product, and certainly others) have not always been consistent. Feedback like this is useful for us to be able to sort through what users expect from the names of these facts, so we can fix it in the future. Generally, changing facts can risk major breakages for existing users, so we try to do so rarely. We'll keep this in mind the next time we look into how we report hardware information. For now, we're unlikely to change it until the next major redesign. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1828) libwhereami does not compile with gcc 7.3.0
Title: Message Title Kranium updated an issue Facter / FACT-1828 libwhereami does not compile with gcc 7.3.0 Change By: Kranium Summary: libwhereami does not compile with gcc 7. 1 3 .0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1828) libwhereami does not compile with gcc 7.1.0
Title: Message Title Kranium created an issue Facter / FACT-1828 libwhereami does not compile with gcc 7.1.0 Issue Type: Bug Assignee: Unassigned Created: 2018/03/02 8:53 PM Priority: Normal Reporter: Kranium libwhereami failed on the NixOS builds when switching to gcc 7.3.0 Current workaround is to use -Wno-error=deprecated -- Build files have been written to: /build/source/build building build flags: -j1 -l1 SHELL=/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/bash Scanning dependencies of target libprojectsrc
Jira (BOLT-57) Download a file
Title: Message Title Michael Smith commented on BOLT-57 Re: Download a file One thing the CLI format I suggested makes weird is working with an inventory. I would suggest we have a separate format like group:/tmp/local_file that we use for groups, where the path is added to each target in the group. Group names are constrained enough that group/tmp/local_file would be unambiguous, but it just looks weird. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-228) Task Plan support
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-228 Task Plan support Issue Type: Task Assignee: Eric Putnam Created: 2018/03/02 3:57 PM Priority: Normal Reporter: Eric Putnam Task Plans live in ./plans/ They are written in the DSL so the existing Puppet parser should be helpful. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3859) Bundle Postgres "pg_repack" extension with PE
Title: Message Title Joel Weierman created an issue PuppetDB / PDB-3859 Bundle Postgres "pg_repack" extension with PE Issue Type: New Feature Assignee: Unassigned Created: 2018/03/02 3:46 PM Priority: Major Reporter: Joel Weierman For large implementations, the size of the tables in the PostgreSQL database can become a major performance bottleneck. These tables require regular vacuuming in order to reduce bloat. However, because the vacuuming process creates an exclusive lock on the table(s) it operates on, it can be difficult to have these operations complete in a timely manner. pg_repack solves this issue by allowing a repack of tables without requiring an exclusive lock. This allows normal database operations to continue during a repack. Bundling this extension in with the Postgres solution (even if it is disabled by default) will provide for a consistent method of repacking tables to everyone. Add Comment
Jira (BOLT-365) Missing period in "E.g." in usage text
Title: Message Title Michael Smith commented on BOLT-365 Re: Missing period in "E.g." in usage text I think we could simplify that down to one example line, and also maybe incorporate groups into the message somehow. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-365) Missing period in "E.g." in usage text
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-365 Missing period in "E.g." in usage text Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-365) Missing period in "E.g." in usage text
Title: Message Title Kate Lopresti commented on BOLT-365 Re: Missing period in "E.g." in usage text TechPubs recommends substituting the English for Latin phrases. Instead of 'e.g.' use 'for example'. **https://confluence.puppetlabs.com/display/Writing/Style+and+formatting#Styleandformatting-Latinphrasesandabbreviations Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-365) Missing period in "E.g." in usage text
Title: Message Title Eric Griswold created an issue Puppet Task Runner / BOLT-365 Missing period in "E.g." in usage text Issue Type: Bug Assignee: Unassigned Created: 2018/03/02 3:30 PM Priority: Trivial Reporter: Eric Griswold $ bolt --version 0.16.4 $ bolt command --help -n, --nodes NODESNode(s) to connect to in URI format [protocol://]host[:port] (Optional) Eg. --nodes bolt.puppet.com Eg. --nodes localhost,ssh://nix.com:,winrm://windows.puppet.com "Eg." should be "E.g."
Jira (BOLT-57) Download a file
Title: Message Title Michael Smith commented on BOLT-57 Re: Download a file Ah, rereading a little I see Henrik wasn't proposing scp-semantics, just a new way of formulating upload and download as a single function with consistent semantics. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-364) Misspelling in usage text
Title: Message Title Eric Griswold created an issue Puppet Task Runner / BOLT-364 Misspelling in usage text Issue Type: Bug Assignee: Unassigned Created: 2018/03/02 3:24 PM Priority: Trivial Reporter: Eric Griswold $ bolt --version 0.16.4 $ bolt command --help --inventoryfile INVENTORY_PATH Specify where to load the invenotry file from "invenotry" s/b "inventory" Add Comment
Jira (BOLT-57) Download a file
Title: Message Title
Michael Smith commented on BOLT-57
Re: Download a file
I like remote_copy as a flexible interface. Underneath, the Transport API would still need to operate with upload/download semantics as not all transports can inter-operate. If you're transferring between things that support scp-semantics (like SSH and SSH) we could have an override implementation for remote_copy. To support a remote_copy on the CLI, we would want to have something similar to scp's syntax for declaring local and remote files. URIs already have a path component that we're not using, which would make sense here. So you would have commands like
bolt file copy local_file.txt ssh://user:password@pluto:22/tmp/local_file.txt
There are some quirks to the above that seem sensible:
an unadorned file is a "local" file, implicitly mapping to a URI like local:///local_file.txt
I chose file copy because that better fits our model of object action. That suggests we should use file_copy for the function rather than remote_copy.
it should otherwise follow the semantics Henrik outlined: Array[Target] -> Target, Target -> Array[Target], Target -> Target are all supported but not array to array.
A with_path helper on Target would be nice so you can pass $target.with_path('/tmp/foo.txt'), or
get_targets($nodes).map |$t| { $t.with_path('/tmp/foo.txt') }
I think adding directories as a source in BOLT-191 would fit onto this cleanly (copy the directory recursively instead of a single file, require that the destination not exist).
Jira (PUP-8230) Puppet Platform Release Process Improvements
Title: Message Title Molly Waggett commented on PUP-8230 Re: Puppet Platform Release Process Improvements Kenn Hussey Casey Williams Justin Stoller Russell Mull I'm closing this Epic, since all improvements we've talked about have been completed. If you'd like to see any other changes, feel free to open a ticket or your own PR. o/\o Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-338) Local transport for bolt
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-338 Local transport for bolt Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Eric Delaney updated an issue Puppet / PUP-6639 Yumrepo can't work with files using spaces in their INI format Change By: Eric Delaney Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-6639 Yumrepo can't work with files using spaces in their INI format Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-227) use markdown as default/only markup type
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-227 use markdown as default/only markup type Issue Type: Task Assignee: Unassigned Created: 2018/03/02 2:12 PM Priority: Normal Reporter: Eric Putnam Let's get rid of the option to specify markdown as the markup. It should only be markdown. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1827) AIX hardwaremodel (os -> hardware) fact is non-standard
Title: Message Title Tommy McNeely created an issue Facter / FACT-1827 AIX hardwaremodel (os -> hardware) fact is non-standard Issue Type: Bug Affects Versions: FACT 3.9.4 Assignee: Unassigned Created: 2018/03/02 1:58 PM Environment: AIX 7.1 TL4 (powerpc) - PE 2017.3.4 (facter 3.9.4) Priority: Normal Reporter: Tommy McNeely Was setting up rspec testing on a module after porting it to AIX and the facts are not being found. Part of the problem is that the default "hardwaremodel" filter is `x86_64`. It does have other OS cases for Solaris (i86pc) and BSD (amd64) for example. While we could add a case for AIX https://github.com/mcanevet/rspec-puppet-facts/issues/69 . The problem is, as I started looking, it looks like the "hardwaremodel" is populated with the actual product name model of the machine (such as "IBM,8284-22A"), while other OS's seem to use something like the processor architecture (x86_64). I think that hardware information belongs in a different fact, like maybe productname (based on what I am seeing on OSX) and the hardwaremodel fact should be "powerpc"
Jira (PDOC-226) Support for Type Aliases
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-226 Support for Type Aliases Issue Type: Task Assignee: Unassigned Created: 2018/03/02 1:45 PM Priority: Normal Reporter: Eric Putnam Support for these would be great: https://puppet.com/docs/puppet/5.3/lang_type_aliases.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-225) Data in Modules?
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-225 Data in Modules? Issue Type: Task Assignee: Unassigned Created: 2018/03/02 1:41 PM Priority: Normal Reporter: Eric Putnam Would like to see documentation created for types, providers, facts and the hiera levels when using data in modules. - Garrett Honeycutt I agree with this but so much of data in modules is dependent on compile time material that it would be impossible to do anything except for defaults (which should be done). However, we do need some way to indicate that a parameter is in module data instead of 'required' that doesn't require keeping a manual mapping (because automation is good, right?) - Trevor Vaughn Add Comment
Jira (PUP-8442) type parameters do not honor when default is set to false
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8442 type parameters do not honor when default is set to false Change By: Josh Cooper Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8442) type parameters do not honor when default is set to false
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8442 type parameters do not honor when default is set to false Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-5915) exec resources fail unless cwd is readable
Title: Message Title James Ralston commented on PUP-5915 Re: exec resources fail unless cwd is readable My first attempt at solving the problem was incorrect, which is why I never submitted a PR. But this is still biting us, so I'll take another crack at it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8442) type parameters do not honor when default is set to false
Title: Message Title Josh Cooper commented on PUP-8442 Re: type parameters do not honor when default is set to false Reverted in https://github.com/puppetlabs/puppet/commit/de6e1f427ebc1f4ed24582468cc671704d093d6b Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-5868) yumrepo does not remove repo file
Title: Message Title James Ralston commented on PUP-5868 Re: yumrepo does not remove repo file Lucas Yamanishi said: Most, if not all repo-release.rpm spec files mark the repo files as %config(noreplace) which will prevent them from being recreated if deleted. This is incorrect. All the %config and %config(noreplace) flags do is to tell rpm that local changes to the file in question must not be lost. (The %config flag retains local changes by moving the current file to .rpmorig; the %config(noreplace) flag retains local changes by installing the new file as .rpmnew. and keeping the current file in place.) But if the file doesn't exist, there are no potential changes to lose, so rpm will always create the file on package install/upgrade. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-723) Due to prefetching, Yumrepo clobbers any definition that it does not create
Title: Message Title Jennifer Solman assigned an issue to Jennifer Solman Puppet / PUP-723 Due to prefetching, Yumrepo clobbers any definition that it does not create Change By: Jennifer Solman Assignee: Jennifer Solman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8442) type parameters do not honor when default is set to false
Title: Message Title Josh Cooper commented on PUP-8442 Re: type parameters do not honor when default is set to false We had to revert this change because the vcsrepo 1.2.0 module defines a "generic" force parameter: newparam :force do desc "Force repository creation, destroying any files on the path in the process." newvalues(:true, :false) defaultto false end Older versions of puppet cause the parameter value to be set to nil, :false or :true, where nil is the default, and the latter two occur if the value is set explicitly in a manifest as "false" or "true", respectively. With the above change, the provider's default false becomes :false, which in ruby is truthy. This causes the vcsrepo type to think force has been set to true and it will attempt to delete the local repo on each run. The incorrect boolean handling in the vcsrepo was fixed in https://github.com/puppetlabs/puppetlabs-vcsrepo/commit/b581a255161fe7fd5d6d264b5c0274ccb852cdcd Add Comment
Jira (PUP-8442) type parameters do not honor when default is set to false
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8442 type parameters do not honor when default is set to false Change By: Josh Cooper Fix Version/s: PUP 5.5.0 Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-362) bolt-inventory-pdb docs are somewhat unclear on how to configure the PuppetDB connection
Title: Message Title Kate Lopresti commented on BOLT-362 Re: bolt-inventory-pdb docs are somewhat unclear on how to configure the PuppetDB connection Added the required file settings, updated the code examples, and made a more obvious link to the PuppetDB docs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-335) Boltlib functions should have configurable timeouts
Title: Message Title Charlie Sharpsteen updated an issue Puppet Task Runner / BOLT-335 Boltlib functions should have configurable timeouts Change By: Charlie Sharpsteen CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8470 Unable to modify local user group membership with forcelocal Change By: Melissa Stone Release Notes Summary: Currently `lusermod` has no way to manage group membership. Puppet is set up so that, in most cases, group membership is managed via the user resource. Now that setting `forcelocal => true` uses `lusermod` instead of `usermod`, we have lost the ability to manage group membership. This change ensures that `usermod` is called only when trying to manage group membership for a user resource. Depending on how the users environment is configured, this may or may not work. If we try to add a user to a NIS or LDAP group, the command will fail. This is consistent with the behavior of group membership management prior to Puppet 5.4.0. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group
Jira (PUP-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Eric Delaney commented on PUP-8470 Re: Unable to modify local user group membership with forcelocal Merged to master at https://github.com/puppetlabs/puppet/commit/1c77bfb8961587ddf5399cd4a70fc908cac6a6ec Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8495) Ubuntu 16.10 _AND NEWER_ use systemd provider as default
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8495 Ubuntu 16.10 _AND NEWER_ use systemd provider as default Change By: Melissa Stone Sub-team: Coremunity Labels: community Team: Platform Core Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (PUP-8495) Ubuntu 16.10 _AND NEWER_ use systemd provider as default
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8495 Ubuntu 16.10 _AND NEWER_ use systemd provider as default Change By: Melissa Stone Labels: community type_and_provider Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8495) Ubuntu 16.10 _AND NEWER_ use systemd provider as default
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8495 Ubuntu 16.10 _AND NEWER_ use systemd provider as default Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8501) Switch to using multi_json
Title: Message Title Maggie Dreyer commented on PUP-8501 Re: Switch to using multi_json In order to maintain backwards compatibility with versions of puppetserver that do not ship MultiJson, I need to add a wrapper module for JSON manipulation in Puppet that will fall back to built-in JSON when MultiJson cannot be loaded. This wrapper can probably be dropped in Puppet 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-263) log bolt results to a log file
Title: Message Title Michal Ruzicka assigned an issue to Michal Ruzicka Puppet Task Runner / BOLT-263 log bolt results to a log file Change By: Michal Ruzicka Assignee: Yasmin Rajabi Michal Ruzicka Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-324) Add automated Bolt testing against Orchestrator
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-324 Add automated Bolt testing against Orchestrator Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-324) Add automated Bolt testing against Orchestrator
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-324 Add automated Bolt testing against Orchestrator Change By: Michael Smith Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8507) move the join() function from stdlib to puppet
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8507 move the join() function from stdlib to puppet Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8491) Move essential functions from stdlib to puppet
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8491 Move essential functions from stdlib to puppet Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8491) Move essential functions from stdlib to puppet
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8491 Move essential functions from stdlib to puppet Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-338) Local transport for bolt
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-338 Local transport for bolt Change By: David Kramer Assignee: Michal Ruzicka Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-332) Target objects should store state of the Targets
Title: Message Title David Kramer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-332 Target objects should store state of the Targets Change By: David Kramer Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-332) Target objects should store state of the Targets
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-332 Target objects should store state of the Targets Change By: Michael Smith Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-324) Add automated Bolt testing against Orchestrator
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-324 Add automated Bolt testing against Orchestrator Change By: David Kramer Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-263) log bolt results to a log file
Title: Message Title Michael Smith assigned an issue to Yasmin Rajabi Puppet Task Runner / BOLT-263 log bolt results to a log file Change By: Michael Smith Assignee: Yasmin Rajabi Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-263) log bolt results to a log file
Title: Message Title Michael Smith commented on BOLT-263 Re: log bolt results to a log file think it's only the title that was confusing, my memory is what you've implemented is what we discussed and the ticket details aren't really clear on the matter. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8502) Puppet lookup always includes classes from the ENC
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8502 Puppet lookup always includes classes from the ENC Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8502) Puppet lookup always includes classes from the ENC
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8502 Puppet lookup always includes classes from the ENC Change By: Thomas Hallgren Fix Version/s: PUP 4.10.11 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7307) Tidy should support 'purge' or update file resource
Title: Message Title Johnson Earls commented on PUP-7307 Re: Tidy should support 'purge' or update file resource I submitted https://github.com/puppetlabs/puppet/pull/6699 for this. The tidy resource currently doesn't check for managed files; reports them in the count of files to be tidied; and tries (but fails) to generate file resources to remove them. My pull request simply filters out any file path that's already managed from the list of files to be tidied. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-263) log bolt results to a log file
Title: Message Title Michal Ruzicka commented on BOLT-263 Re: log bolt results to a log file Alex Dreyer, Yasmin Rajabi, I was confused by / didn't properly read the description of this ticket and rather then implementing support for writing the results into file(s), I implemented support for writing log messages into file(s). Should we rename this ticket to reflect the fact and create a new one to track the support for writing the results into the file(s)? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8507) move the join() function from stdlib to puppet
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8507 move the join() function from stdlib to puppet Issue Type: Improvement Assignee: Henrik Lindberg Created: 2018/03/02 6:20 AM Priority: Normal Reporter: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (PUP-8496) move keys() and values() functions from stdlib to puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8496 move keys() and values() functions from stdlib to puppet Change By: Henrik Lindberg Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8492) Move the empty() function from stdlib to puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8492 Move the empty() function from stdlib to puppet Change By: Henrik Lindberg Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8497) move the length() function from stdlib to puppet
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8497
move the length() function from stdlib to puppet
Change By:
Henrik Lindberg
Sub-team:
Language
Release Notes Summary:
The function {{length}} has moved from stdlib to puppet. It is compatible with the length function in stdlib (and the deprecated {{size}} function), and adds support for also returning the length of a {{Binary}} value.
Team:
Platform Core
Sprint:
Platform Core KANBAN
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8497) move the length() function from stdlib to puppet
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8497 move the length() function from stdlib to puppet Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8497) move the length() function from stdlib to puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8497 move the length() function from stdlib to puppet Change By: Henrik Lindberg Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8506) USers reporting issue with Puppet yum repos
Title: Message Title Adam Buxton created an issue Puppet / PUP-8506 USers reporting issue with Puppet yum repos Issue Type: Bug Assignee: Unassigned Created: 2018/03/02 3:03 AM Priority: Normal Reporter: Adam Buxton a repository sync error from http://yum.puppetlabs.com/el/7/PC1/x86_64/repodata/ This file does not exist: Retrieving 'repodata/f83ba39771b2550d5d00bc665bdb797e328ae3a1-primary.sqlite.bz2' failed: File not found in repository 'puppetlabs-el7-x86_64' Please fix your repodata Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-7307) Tidy should support 'purge' or update file resource
Title: Message Title Matthias Baur commented on PUP-7307 Re: Tidy should support 'purge' or update file resource Yes please! I ran into the following problem today: We need to purge all "/etc/sysconfig/network-scripts/ifcfg-bond.*" files which aren't managed by Puppet. Currently this isn't really possible due to: I need to maintain a ignore list for a file resources which purges the directory Tidy would do it, but all prints "Tidying x files" on every Puppet run which spams our log Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8482) Create a formal representation of the AST that can replace the current dump format
Title: Message Title Henrik Lindberg commented on PUP-8482 Re: Create a formal representation of the AST that can replace the current dump format Merged to puppet master. Some minor changes requested on the specification. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8482) Create a formal representation of the AST that can replace the current dump format
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8482 Create a formal representation of the AST that can replace the current dump format Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8492) Move the empty() function from stdlib to puppet
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8492 Move the empty() function from stdlib to puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8492) Move the empty() function from stdlib to puppet
Title: Message Title Thomas Hallgren commented on PUP-8492 Re: Move the empty() function from stdlib to puppet Merged to master at 8bbea52. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8496) move keys() and values() functions from stdlib to puppet
Title: Message Title Thomas Hallgren commented on PUP-8496 Re: move keys() and values() functions from stdlib to puppet Merged to master at 9804a1b. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8496) move keys() and values() functions from stdlib to puppet
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8496 move keys() and values() functions from stdlib to puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
