Jira (PUP-8901) Puppet5 server does not work with Puppet4 termini
Title: Message Title Eric Sorenson commented on PUP-8901 Re: Puppet5 server does not work with Puppet4 termini you can't have mixed major versions among puppet db/server/agent (agent package installed on master, i mean - you can have older agents checking in to newer masters, of course). if the docs don't explicitly call that out they ought to. 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-546) mktemp is not available on all platform (AIX specifically)
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-546 mktemp is not available on all platform (AIX specifically) 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-536) Default input method of PowerShell files does not appear to be powershell, but STDIN
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-536 Default input method of PowerShell files does not appear to be powershell, but STDIN 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 (PUP-8735) File resource doesn't seem to parse UTF8 filenames when recursively copying directories
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8735 File resource doesn't seem to parse UTF8 filenames when recursively copying directories Change By: Ethan Brown Sprint: Platform Core Windows 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-8735) File resource doesn't seem to parse UTF8 filenames when recursively copying directories
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8735 File resource doesn't seem to parse UTF8 filenames when recursively copying directories Change By: Ethan Brown Team: Coremunity Windows 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-8842) Package module into puppet-agent
Title: Message Title Josh Cooper commented on PUP-8842 Re: Package module into puppet-agent Merged to puppet-agent#master in https://github.com/puppetlabs/puppet-agent/commit/ac97ae51faf4549337ebfe6d66cb0d23fdd43ac0 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-546) mktemp is not available on all platform (AIX specifically)
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-546 mktemp is not available on all platform (AIX specifically) Change By: Nick Lewis Assignee: Nick Lewis 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-256) REFERENCE.md in CI
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-256 REFERENCE.md in CI Issue Type: Task Assignee: Eric Putnam Created: 2018/06/04 3:01 PM Priority: Normal Reporter: Eric Putnam Ticket to track work around getting automation of REFERENCE.md up and running for modules. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8871) Remove type/provider code from puppet
Title: Message Title Josh Cooper commented on PUP-8871 Re: Remove type/provider code from puppet Merged to master in https://github.com/puppetlabs/puppet/commit/70d518ff1db5280387e4eea97feb25356d6c08d8 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-8864) Remove type/provider code from puppet
Title: Message Title Josh Cooper commented on PUP-8864 Re: Remove type/provider code from puppet Merged to master in https://github.com/puppetlabs/puppet/commit/70d518ff1db5280387e4eea97feb25356d6c08d8 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-8896) Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Title: Message Title Josh Cooper commented on PUP-8896 Re: Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load Marking this as fix version 6.0, but we'll need to make sure the deprecation warning in 5.5.x doesn't have the same issue. 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-8896) Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8896 Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load Change By: Josh Cooper 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 (PUP-8896) Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Title: Message Title Josh Cooper assigned an issue to Kris Bosland Puppet / PUP-8896 Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load Change By: Josh Cooper Assignee: Kris Bosland 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-8896) Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8896 Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load Change By: Josh Cooper Team: Coremunity 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-8896) Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Title: Message Title Nick Lewis commented on PUP-8896 Re: Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load I wasn't doing anything with this. I just encountered it while tracking down another bug. 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-8900) "puppet facts upload" face only tries first master in server_list
Title: Message Title Josh Cooper commented on PUP-8900 Re: "puppet facts upload" face only tries first master in server_list Thanks Branan Riley, makes sense. FYI, we've started on a sane http client implementation which supports server_list failover (and SRV records): https://github.com/puppetlabs/puppet/blob/b8759ca8eedf28b132b2488affec1668bb09994b/lib/puppet/rest/route.rb#L70-L88. I'll add this ticket to the Agent HTTP epic. One of the goals is going to be normalizing the various http implementations and migrating call sites over to use the new http client. 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-7407) Add deprecation warning to Puppet::Util.absolute_path?
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-7407 Add deprecation warning to Puppet::Util.absolute_path? Change By: Jorie Tappa Assignee: Jorie Tappa 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-8900) "puppet facts upload" face only tries first master in server_list
Title: Message Title Branan Riley commented on PUP-8900 Re: "puppet facts upload" face only tries first master in server_list IIRC we had a ticket somewhere to make the docs more clear that failover only occurred in the agent application. I have no idea what the disposition of that ticket ended up being. 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-8902) Re-word "Failed to load library" debug message
Title: Message Title Josh Cooper commented on PUP-8902 Re: Re-word "Failed to load library" debug message Charlie Sharpsteen I'm going to close this as a dup of PUP-8586 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-8900) "puppet facts upload" face only tries first master in server_list
Title: Message Title Branan Riley commented on PUP-8900 Re: "puppet facts upload" face only tries first master in server_list We intentionally kept the scope to the agent application due to the complexities of how it's plumbed hacked into the networking code right now. Ideally once we have less-magical networking client code in the agent, with failover as a first-class citizen, we can enable it in other applications. 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-8897) check_manage_home useradd provider needs to add -M on Debian
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8897
check_manage_home useradd provider needs to add -M on Debian
Change By:
Josh Cooper
Regarding the code here:[https://github.com/puppetlabs/puppet/blob/1c77bfb8961587ddf5399cd4a70fc908cac6a6ec/lib/puppet/provider/user/useradd.rb#L127-L135]There is an edge case that is missed. If force_local is true and manage_home is false, then "-M" should be added as a command line argument on Debian Jessie (and possibly others).If this is not in place, a bug occurs as follows when running on Debian Jessie (and possibly others). First manually create `/home/bob` (like pam_mkhomedir might do) and then try to add `bob` with a resource like this, and it will fail: {code:puppet} user { 'bob': force_local => true, manage_home => false, ... Other Params ...} {code}
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
Jira (PUP-8896) Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Title: Message Title Josh Cooper commented on PUP-8896 Re: Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load Thanks Nick Lewis, were you taking a look at this or should Kris Bosland? 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-8900) "puppet facts upload" face only tries first master in server_list
Title: Message Title Josh Cooper commented on PUP-8900 Re: "puppet facts upload" face only tries first master in server_list Thanks Jesse Reynolds. Only the agent correctly handles server_list. Branan Riley do you know if there were plans on adding server_list handling to other applications? 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-8900) "puppet facts upload" face only tries first master in server_list
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8900 "puppet facts upload" face only tries first master in server_list Change By: Josh Cooper Team: Coremunity 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-8901) Puppet5 server does not work with Puppet4 termini
Title: Message Title Josh Cooper commented on PUP-8901 Re: Puppet5 server does not work with Puppet4 termini Puppetserver 5 is not 100% compatible with puppetdb 4 termini. See PDB-3620, PDB-3527 and https://github.com/puppetlabs/puppetdb/commit/a79b4a795966c45b91dacfa79ec8eafab150756f#diff-af5e1b6bc26e077e1da4e4d942fcf2de. My understanding is that puppetdb, puppetdb termini and puppetserver need to upgraded in tandem. Is there something preventing you from upgrading to puppetdb 5, then the puppetdb termini and puppetserver packages? 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-8893) external, executable facts via pluginsync get executable flag removed
Title: Message Title Josh Cooper commented on PUP-8893 Re: external, executable facts via pluginsync get executable flag removed Puppet has always required that external facts in modules have their execute bit set on the master, and pluginsync preserves the executable-ness during pluginsync. If you make the external fact executable on the server, then it should resolve this issue. Please verify and close this ticket. Relying on source permissions is problematic. For example, if you're using r10k, then you have to make sure the execute bit is set correctly in git. Also the owner/group on the server may not make sense on the agent. We want to move away from pluginsync using source permissions. See PUP-5920 and PUP-5921. The solution will need to take into account that not all pluginsync'ed facts should be executed everywhere (windows vs *nix). 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-8893) external, executable facts via pluginsync get executable flag removed
Title: Message Title Josh Cooper assigned an issue to Martin Alfke Puppet / PUP-8893 external, executable facts via pluginsync get executable flag removed Change By: Josh Cooper Assignee: Martin Alfke 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-8582) Add vendor_modules to basemodulepath
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8582 Add vendor_modules to basemodulepath Change By: Josh Cooper Release Notes Summary: Puppet's default basemodulepath now includes a vendored modules directory, which enables puppet to load modules that are vendored in the puppet-agent package. To prevent puppet from loading modules from this directory, change the basemodulepath back to its previous value, e.g. on *nix "$codedir/modules:/opt/puppetlabs/puppet/modules". On Windows: "$codedir/modules" Release Notes: New Feature 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-8904) Yumrepo should accept arbitrary custom parameters
Title: Message Title
Melissa Stone updated an issue
Puppet / PUP-8904
Yumrepo should accept arbitrary custom parameters
Change By:
Melissa Stone
Yum allows arbitrary parameters in a repo config file. Invalid or non-functional parameters are ignored when the file is parsed. There is a possibility of someone writing a custom yum module that accepts additional repo parameters, and puppet should not be responsible for supporting and documenting these new parameters. Rather, puppet should provide a mechanism for users to define custom values in addition to the top level supported parameters we currently have. Something like * a hash of custom parameters * would be ideal. For additional discussion, see https://github.com/puppetlabs/puppet/pull/6834#discussion_r191387514One use case is amazon linux. They support two additional parameters that we do not have support for: {{report_instanceid}} and {{fastestmirror_enabled}}. Support for both of these has been added to [voxpupuli/puppet-yum|https://github.com/voxpupuli/puppet-yum/blob/eab4716627adc8ac6aa82ba7185e45f50d684ea5/data/os/RedHat/Amazon.yaml#L28]. However, because yumrepo doesn't support these parameters, {{puppet apply}} fails to apply these manifests. {{report_instanceid}} is very specific to the amazon repo setup, but there is [documentation|https://aws.amazon.com/amazon-linux-ami/faqs/] for it. However, there is no evidence there is any documentation or support or functionality to {{fastmirror_enabled}}. Amazon simply has it as a parameter for their repo configs. Rather than add a top level parameter to yum repo for either of these very special parameters, we should open a path for users to access these parameters without any burden on puppet to verify these are valid and functional parameters.
Add Comment
Jira (PUP-8904) Yumrepo should accept arbitrary custom parameters
Title: Message Title
Melissa Stone updated an issue
Puppet / PUP-8904
Yumrepo should accept arbitrary custom parameters
Change By:
Melissa Stone
Yum allows arbitrary parameters in a repo config file. Invalid or non-functional parameters are ignored when the file is parsed. There is a possibility of someone writing a custom yum module that accepts additional repo parameters, and puppet should not be responsible for supporting and documenting these new parameters. Rather, puppet should provide a mechanism for users to define custom values in addition to the top level supported parameters we currently have.Something like a hash of custom parameters would be ideal. For additional discussion, see https://github.com/puppetlabs/puppet/pull/6834#discussion_r191387514 One use case is amazon linux. They support two additional parameters that we do not have support for: {{report_instanceid}} and {{fastestmirror_enabled}}. Support for both of these has been added to [voxpupuli/puppet-yum|https://github.com/voxpupuli/puppet-yum/blob/eab4716627adc8ac6aa82ba7185e45f50d684ea5/data/os/RedHat/Amazon.yaml#L28]. However, because yumrepo doesn't support these parameters, {{puppet apply}} fails to apply these manifests. {{report_instanceid}} is very specific to the amazon repo setup, but there is [documentation|https://aws.amazon.com/amazon-linux-ami/faqs/] for it. However, there is no evidence there is any documentation or support or functionality to {{fastmirror_enabled}}. Amazon simply has it as a parameter for their repo configs. Rather than add a top level parameter to yum repo for either of these very special parameters, we should open a path for users to access these parameters without any burden on puppet to verify these are valid and functional parameters.
Add Comment
Jira (PUP-8904) Yumrepo should accept arbitrary custom parameters
Title: Message Title
Melissa Stone updated an issue
Puppet / PUP-8904
Yumrepo should accept arbitrary custom parameters
Change By:
Melissa Stone
Yum allows arbitrary parameters in a repo config file. Invalid or non-functional parameters are ignored when the file is parsed. There is a possibility of someone writing a custom yum module that accepts additional repo parameters, and puppet should not be responsible for supporting and documenting these new parameters. Rather, puppet should provide a mechanism for users to define custom values in addition to the top level supported parameters we currently have. One use case is amazon linux. They support two additional parameters that we do not have support for: {{report_instanceid}} and {{fastestmirror_enabled}}. Support for both of these has been added to [voxpupuli/puppet-yum|https://github.com/voxpupuli/puppet-yum/blob/eab4716627adc8ac6aa82ba7185e45f50d684ea5/data/os/RedHat/Amazon.yaml#L28]. However, because yumrepo doesn't support these parameters, {{puppet apply}} fails to apply these manifests. {{ report_instaneid report_instanceid }} is very specific to the amazon repo setup, but there is [documentation|https://aws.amazon.com/amazon-linux-ami/faqs/] for it. However, there is no evidence there is any documentation or support or functionality to {{fastmirror_enabled}}. Amazon simply has it as a parameter for their repo configs. Rather than add a top level parameter to yum repo for either of these very special parameters, we should open a path for users to access these parameters without any burden on puppet to verify these are valid and functional parameters.
Add Comment
Jira (PUP-8904) Yumrepo should accept arbitrary custom parameters
Title: Message Title Melissa Stone created an issue Puppet / PUP-8904 Yumrepo should accept arbitrary custom parameters Issue Type: Improvement Assignee: Unassigned Components: Types and Providers Created: 2018/06/04 9:40 AM Fix Versions: PUP 6.y Priority: Normal Reporter: Melissa Stone Yum allows arbitrary parameters in a repo config file. Invalid or non-functional parameters are ignored when the file is parsed. There is a possibility of someone writing a custom yum module that accepts additional repo parameters, and puppet should not be responsible for supporting and documenting these new parameters. Rather, puppet should provide a mechanism for users to define custom values in addition to the top level supported parameters we currently have. One use case is amazon linux. They support two additional parameters that we do not have support for: report_instanceid and fastestmirror_enabled. Support for both of these has been added to voxpupuli/puppet-yum. However, because yumrepo doesn't support these parameters, puppet apply fails to apply these manifests. report_instaneid is very specific to the amazon repo setup, but there is documentation for it. However, there is no evidence there is any documentation or support or functionality to fastmirror_enabled. Rather than add a top level parameter to yum repo for either of these very special parameters, we should open a path for users to access these parameters without any burden on puppet to verify these are valid and functional parameters.
Jira (BOLT-534) Bolt hangs when no sudo password is provided
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-534 Bolt hangs when no sudo password is provided 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 (PDB-3857) Fix fact path GC incompatibility with Postgres 10
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3857 Fix fact path GC incompatibility with Postgres 10 Change By: Rob Browning Summary: Postgres 10 error in Fix fact path GC incompatibility with Postgres 10 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 (PDB-3490) Get rbac-client version from clj-parent in pdbext
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3490 Get rbac-client version from clj-parent in pdbext Change By: Rob Browning Assignee: Rob Browning 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 (PDB-3917) Stop sed-ing project file for tests, and unify test dep handling
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3917 Stop sed-ing project file for tests, and unify test dep handling Change By: Rob Browning Assignee: Rob Browning 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 (PDB-3490) Get rbac-client version from clj-parent in pdbext
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3490 Get rbac-client version from clj-parent in pdbext Change By: Rob Browning Assignee: Rob Browning Sprint: Hopper/Triage Data Platform 2018-06-06 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 (PDB-3917) Stop sed-ing project file for tests, and unify test dep handling
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3917 Stop sed-ing project file for tests, and unify test dep handling Change By: Rob Browning Assignee: Rob Browning Story Points: 1 Sprint: Hopper/Triage Data Platform 2018-06-06 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 (PDB-3917) Stop sed-ing project file for tests, and unify test dep handling
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3917 Stop sed-ing project file for tests, and unify test dep handling Change By: Rob Browning Summary: See if we can use "lein change set '"foo"' to improve extensions Stop sed-ing project editing file for tests, and unify test dep handling 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-8903) Allow "puppet agent --disable" via Console > Run Puppet
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-8903 Allow "puppet agent --disable" via Console > Run Puppet Change By: Halim Wijaya Issue Type: Improvement New Feature 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-8903) Allow "puppet agent --disable" via Console > Run Puppet
Title: Message Title Halim Wijaya created an issue Puppet / PUP-8903 Allow "puppet agent --disable" via Console > Run Puppet Issue Type: Improvement Assignee: Unassigned Created: 2018/06/04 1:38 AM Priority: Normal Reporter: Halim Wijaya PE was shipped with MCollective that can disable puppet agent with command mco puppet disable Now with MCollective being deprecated and eventually replaced by Task, there is no "built-in" option to disable puppet agents. Would be great if we can have that option via Console UI. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
