Jira (BOLT-305) Task metadata should allow defaults for parameter values
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-305 Task metadata should allow defaults for parameter values Change By: Alex Dreyer 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 (PUP-7509) Phase 1.1 Puppet Unicode Adoption Blockers
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7509 Phase 1.1 Puppet Unicode Adoption Blockers Change By: Geoff Nichols Labels: i18n utf-8 ☃ 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-1229) Support temporary directory on Windows over SSH
Title: Message Title Alex Dreyer commented on BOLT-1229 Re: Support temporary directory on Windows over SSH It seems like there are larger issues around trying to use ssh to connect to windows proper(ie not cygwin or WSL). Won't we need to use the majority of the logic in Bolt::Transport::Powershell? It will definitely require some changes to how we handle sudo and features. If we discover that is the case we should probably make this ticket more generic something along the lines of support ssh transport to windows targets. 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-1229) Support temporary directory on Windows over SSH
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1229 Support temporary directory on Windows over SSH Change By: Alex Dreyer Labels: 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 (BOLT-1231) Use targets instead of nodes in v2 inventory
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1231
Use targets instead of nodes in v2 inventory
Change By:
Alex Dreyer
Release Notes Summary:
This allows {{--targets}} to be used in place of {{--nodes}} as a commandline flag.
Release Notes:
Enhancement
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-3705) Puppet agent is using puppet master fact terminus setting in routes.yaml
Title: Message Title Josh Cooper commented on PUP-3705 Re: Puppet agent is using puppet master fact terminus setting in routes.yaml Wow this is still an issue: # puppet agent -t --http_debug ... <- "GET /pdb/query/v4/nodes/puppet/facts HTTP/1.1\r\nAccept: application/json\r\nContent-Type: application/x-www-form-urlencoded; charset=UTF-8\r\nAccept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3\r\nUser-Agent: Puppet/6.0.4 Ruby/2.5.1-p57 (x86_64-linux)\r\nHost: puppetdb:8081\r\n\r\n" -> "HTTP/1.1 200 OK\r\n" -> "Date: Wed, 17 Apr 2019 22:39:51 GMT\r\n" -> "Content-Type: application/json;charset=utf-8\r\n" -> "Vary: Accept-Encoding, User-Agent\r\n" -> "Content-Encoding: gzip\r\n" -> "Content-Length: 1723\r\n" -> "Server: Jetty(9.4.z-SNAPSHOT)\r\n" -> "\r\n" reading 1723 bytes...
Jira (PUP-4370) Formalize Types and Providers API
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4370 Formalize Types and Providers API Change By: Josh Cooper Team/s: Platform Core 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-7509) Phase 1.1 Puppet Unicode Adoption Blockers
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7509 Phase 1.1 Puppet Unicode Adoption Blockers Change By: Josh Cooper Team/s: Platform Core 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 (BOLT-943) Target object should have clear, documented API
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-943
Target object should have clear, documented API
Change By:
Alex Dreyer
Currently the data type {{Target}} accepts a URI, and an options hash. What works in that options hash is undocumented. I've primarily gotten extra options {{ssl}} and {{host-key-check}} to work, but others that may be associated with the URI do not work. - user - password - protocol - portWe should make these work as additional options (and document them).Notes Are all nodes that get mentioned part of the "all" group? *Hypothesis*: no, nodes not added are not part of the group. If you have multiple inventory sources, then 'all' is all sources, 'all:aws' is all nodes from an aws inventory. All isn't very useful in a plan anyway, so it's not hugely important.Targets are singletons by their name.How should update functions handle a target spec/string/array of targets? It should accept an array of targets (later work). add notes to ticket.Problems with options: - options set on a Target instance are not saved on the singleton - get_targets is the only way to get targets Target.new is deprecated - get_target is new function to get a single target. - support set config/options function for a target will set same config schema as inventory- add_to_group may change the priority order of certain optionsOther known issues with Target- Targets without a name but no uri are stringified strangely as Target('', { }).- There is not a good way to get a "short" or "safe" name that can be printed for targets without exposing sensitive information or ugly protocol characters.- There is no way to override values in the uri. Is this a problem?Use cases: - I want to create a new Target from scratch - I want to change the transport of a target. - I want to set a transport config option on a specific target. - I want to set a transport config on a number of targets.Work for this ticket: - allow config in inventory to be updated with puppet functions like vars and facts. - add new get_target function that will get a single target or error. - deprecate creating target objects without get_targets. How are options updated when new config is added? Do we support targets without an inventory ref or error? - Targets should always have a reference back to the inventory. - We expect all targets created/found by get_targets/get_target to inherit config from top-level of inventory (i.e. they're implicitly part of the "all" group). - Add new {{config}} (returns entire config which needs to be frozen) and {{add_config}} as getters and setters of config options on a single target.- Don't concern ourselves with {{options}}, act as though it may be deprecated Examples for add_config (these are not considered ideal, but the best we've come up with): Overwrite any existing SSH config: {{add_config($target, 'ssh', \{ 'user' => 'ubuntu' })}} Set only the ssl-verify option: {{add_config($target, ['winrm', 'ssl-verify'], 'false')}}
Jira (BOLT-943) Target object should have clear, documented API
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-943
Target object should have clear, documented API
Change By:
Alex Dreyer
Currently the data type {{Target}} accepts a URI, and an options hash. What works in that options hash is undocumented. I've primarily gotten extra options {{ssl}} and {{host-key-check}} to work, but others I wanted to use didn't: that may be associated with the URI do not work. - user - password - protocol - portWe should make these work as additional options (and document them).Notes Are all nodes that get mentioned part of the "all" group? *Hypothesis*: no, nodes not added are not part of the group. If you have multiple inventory sources, then 'all' is all sources, 'all:aws' is all nodes from an aws inventory. All isn't very useful in a plan anyway, so it's not hugely important.Targets are singletons by their name.How should update functions handle a target spec/string/array of targets? It should accept an array of targets (later work). add notes to ticket.Problems with options: - options set on a Target instance are not saved on the singleton - get_targets is the only way to get targets Target.new is deprecated - get_target is new function to get a single target. - support set config/options function for a target will set same config schema as inventory - add_to_group may change the priority order of certain options Other known issues with Target- Targets without a name but no uri are stringified strangely as Target('', { }).- There is not a good way to get a "short" or "safe" name that can be printed for targets without exposing sensitive information or ugly protocol characters.- There is no way to override values in the uri. That is out Is this a problem?Use cases:I want to create a new Target from scratchI want to change the transport of scope a target . I want to set a transport config option on a specific target. I want to set a transport config on a number of targets. Work for this ticket: - allow config in inventory to be updated with puppet functions like vars and facts. - add new get_target function that will get a single target or error. - deprecate creating target objects without get_targets. How are options updated when new config is added? Do we support targets without an inventory ref or error? - Targets should always have a reference back to the inventory. - We expect all targets created/found by get_targets/get_target to inherit config from top-level of inventory (i.e. they're implicitly part of the "all" group). - Add new {{config}} (returns entire config which needs to be frozen) and {{add_config}} as getters and setters of config options on a single target.- Don't concern ourselves with {{options}}, act as though it may be deprecated Examples for add_config (these are not considered ideal, but the best we've come up with): Overwrite any existing SSH config: {{add_config($target, 'ssh', \{ 'user' => 'ubuntu' })}} Set only the ssl-verify option: {{add_config($target, ['winrm', 'ssl-verify'], 'false')}}
Jira (PUP-9182) Agent server_list HA
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9182 Agent server_list HA Change By: Josh Cooper Epic Name: Agent server_list HA 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-9182) Agent server_list HA
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9182 Agent server_list HA Change By: Josh Cooper Summary: Agent server_list HA 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-1519) Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1519 Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number Change By: Josh Cooper Team/s: Platform Core 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-7267) Execution API
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7267 Execution API Change By: Josh Cooper Rewrite Create a new Puppet::Util::Execution API that can exist side-by-side with existing implementation . Handle Unicode and , binary content, passing stdin, streaming in/out/err, environment variables, runas correctly across platforms . 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-7267) Execution API
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7267 Execution API Change By: Josh Cooper Epic Name: rewrite Puppet::Util:: Execution API 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-7267) Execution API
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7267 Execution API Change By: Josh Cooper Summary: rewrite Puppet::Util:: Execution API 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-7550) Revisit SRV support in the agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7550 Revisit SRV support in the agent Change By: Josh Cooper SRV records provide a way for agents to dynamically determine which host to connect to for a given service, eg ca vs compiler vs report server. SRV provides high-availability (the SRV record can contain multiple hosts to connect to) and allows agents to connect to the "closest" host providing that service. Puppet has supported SRV records for awhile, but there were issues due to the global nature of the indirector. As we move to no longer using the indirector for HTTP/REST requests, we should reexamine the issues below and ensure SRV support is first-class. 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
Jira (PUP-7550) Revisit SRV support in the agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7550 Revisit SRV support in the agent Change By: Josh Cooper Summary: Revisit SRV support in the agent 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-7097) Support progress reporting for long-running commands invoked by providers during "puppet apply"
Title: Message Title Josh Cooper commented on PUP-7097 Re: Support progress reporting for long-running commands invoked by providers during "puppet apply" Getting progress notifications would be a good thing, but I think it's only really practical to implement if the provider programmatically calls (in your example) libcurl instead of curl. For example, libcurl allows the caller to provide a progress notification callback: CURLcode curl_easy_setopt(CURL *handle, CURLOPT_PROGRESSFUNCTION, progress_callback); That said, we don't have plans to add notifications to the current type and provider API, and the future remains to be seen. I'm going to close this for now, but will keep it in mind for the future. 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
Jira (PUP-9647) Pip package provider should use execute for Windows compatibility
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9647 Pip package provider should use execute for Windows compatibility Change By: Jarret Lavallee Labels: maintenance triage Team: Puppet Romania Method Found: Needs Assessment Customer Feedback 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-9647) Pip package provider should use execute for Windows compatibility
Title: Message Title Sean Millichamp commented on PUP-9647 Re: Pip package provider should use execute for Windows compatibility I have created two PRs which seem to resolve the issue: against master: https://github.com/puppetlabs/puppet/pull/7487 against 5.5.x: https://github.com/puppetlabs/puppet/pull/7488 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-9647) Pip package provider should use execute for Windows compatibility
Title: Message Title Sean Millichamp created an issue Puppet / PUP-9647 Pip package provider should use execute for Windows compatibility Issue Type: Bug Affects Versions: PUP 6.4.0, PUP 5.5.10 Assignee: Unassigned Components: Types and Providers Created: 2019/04/17 1:39 PM Priority: Normal Reporter: Sean Millichamp The package pip provider has some suggestion of Windows support. However, it uses "execpipe" to invoke commands, which puts a shell redirection of "2>&1" into the final command which is not compatible with Windows. On a Windows system with Python installed when the "pip_version" method is called it results in an error: "Cannot collect packages for Puppet::Type::Package::ProviderPip3 provider; undefined method `[]' for nil:NilClass" Reworking this in terms of execute allows the pip provider to work on Windows as well. Add Comment
Jira (PUP-8587) Rich Data support (Binary and others) in Puppet 6.y
Title: Message Title Josh Cooper commented on PUP-8587 Re: Rich Data support (Binary and others) in Puppet 6.y Henrik Lindberg Maggie Dreyer what's the status of this? 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-4253) Use fixed refs rather than branch tips for published docs
Title: Message Title Rob Browning commented on PDB-4253 Re: Use fixed refs rather than branch tips for published docs This is no longer relevant, and I'll close it and the related pr once we create the foo-doc branches we've decided with the doc team to pursue instead. 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-4255) Fix deprecation warnings from clojure 1.10 upgrade
Title: Message Title Rob Browning assigned an issue to Unassigned PuppetDB / PDB-4255 Fix deprecation warnings from clojure 1.10 upgrade 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-3311) Improve error message on "index row size" exceptions
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3311 Improve error message on "index row size" exceptions Change By: Rob Browning Team: PuppetDB 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-3311) Improve error message on "index row size" exceptions
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3311 Improve error message on "index row size" exceptions 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-3592) HA - Failure syncing to replica - file not found - after promotion
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3592 HA - Failure syncing to replica - file not found - after promotion Change By: Rob Browning Team: Organizational Scale PuppetDB 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-3592) HA - Failure syncing to replica - file not found - after promotion
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3592 HA - Failure syncing to replica - file not found - after promotion 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 (PUP-9645) User Rights Management SIP issue on MacOS 10.14.x
Title: Message Title Marshall Taylor commented on PUP-9645 Re: User Rights Management SIP issue on MacOS 10.14.x Gheorghe Popescu - I would be happy to test out a nightly build. So, my issue is related to issue raised in PUP-9502? 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-9645) User Rights Management SIP issue on MacOS 10.14.x
Title: Message Title
Gheorghe Popescu commented on PUP-9645
Re: User Rights Management SIP issue on MacOS 10.14.x
Marshall Taylor I run successfully the following manifest on an agent that contains PUP-9502 fixes
user { 'company_admin13':
ensure => 'present',
comment => 'company Administrator',
gid => '20',
groups => ['admin'],
home => '/var/company_admin13',
iterations => '28328',
shell => '/bin/bash',
password => 'pwd',
salt => 'salt',
uid => 411
}
file { '/var/company_admin13':
Jira (PUP-9645) User Rights Management SIP issue on MacOS 10.14.x
Title: Message Title
Marshall Taylor commented on PUP-9645
Re: User Rights Management SIP issue on MacOS 10.14.x
Gheorghe Popescu below is a config file that I believe will trigger the failure: class company_mac::config inherits company_mac { $munkitools_version = '3.6.0.3733' $simian_version = '2.5' $puppet_major_version = '6' $puppet_version = '6.3.0' $puppet_os_version = '10.13' # leave manually set to slightly old version, as current version not available package { "puppet-agent-${puppet_version}-1.osx${puppet_os_version}.dmg": ensure => 'present', provider => 'pkgdmg', source => "https://downloads.puppetlabs.com/mac/puppet${puppet_major_version}/${puppet_os_version}/x86_64/puppet-agent-${puppet_version}-1.osx${puppet_os_version}.dmg", } macdefaults { 'Hide local admin account': domain => '/Library/Preferences/com.apple.loginwindow', key => 'Hide500Users', type => 'boolean', value => true, } if $facts['remote_login'] == false { exec {'Turn on sshd': command => '/usr/sbin/systemsetup -f -setremotelogin on', } } user { 'company_admin': ensure => 'present', comment => 'company Administrator', gid => '20', groups => ['admin'], home => '/var/company_admin', iterations => '28328', # lint:ignore:140chars password => '[passwd]', # lint:endignore salt => '[salt]', shell => '/bin/bash', uid => '499', } file { '/var/company_admin': ensure => directory, owner => 'company_admin', group => 'wheel', mode => '0700', require => User['company_admin'], } }
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4346) Update sync deduplication to account for configure-expiration commands
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4346 Update sync deduplication to account for configure-expiration commands Issue Type: Bug Assignee: Unassigned Created: 2019/04/17 9:12 AM Priority: Normal Reporter: Zachary Kent When merging up the sync deduplication work we forgot to add an entry for configure-expiration commands to the lookup map used to populate the atom that tracks the contents of the queue. We'll need to fix this so configure-expiration commands are properly tracked. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1232) Document experimental v2 Inventory
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1232 Document experimental v2 Inventory Change By: Cas Donoghue Assignee: Cas Donoghue 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-1244) SELinux management does not work on localhost
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1244 SELinux management does not work on localhost Change By: Cas Donoghue Assignee: Cas Donoghue 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-4346) Update sync deduplication to account for configure-expiration commands
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4346 Update sync deduplication to account for configure-expiration commands Change By: Zachary Kent When merging up the sync deduplication work we forgot to add an entry for configure-expiration commands to the lookup map used to populate the atom that tracks the contents of the queue. We'll need to fix this so configure-expiration commands are properly tracked. As a result configure-expiration commands will be duplicated across sync restarts. 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-4346) Update sync deduplication to account for configure-expiration commands
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4346 Update sync deduplication to account for configure-expiration commands Change By: Zachary Kent Assignee: Zachary Kent 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-1257) Support Encrypted password in bolt.yaml
Title: Message Title Patrick Lesher created an issue Puppet Task Runner / BOLT-1257 Support Encrypted password in bolt.yaml Issue Type: New Feature Assignee: Unassigned Components: bolt, SSH, Windows Created: 2019/04/17 8:31 AM Priority: Normal Reporter: Patrick Lesher Our operations team would like to use bolt for animated tasks ( Jenkins ) but do not want to keep an Admin password in plain txt in the bolt.yaml file. Bolt should support encrypted password in the bolt.yaml file and/or be able to pull passwords from other sources ( hiera, kerberos, AD, etc ). Add Comment
Jira (BOLT-1102) Move `unwrap_sensitive_args` to common location
Title: Message Title Lucy Wyman commented on BOLT-1102 Re: Move `unwrap_sensitive_args` to common location This doesn't seem to still be an issue. Nothing to do 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-9639) Windows package resource does not remove trailing whitespace
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-9639 Windows package resource does not remove trailing whitespace Change By: Gheorghe Popescu Assignee: Gheorghe Popescu 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-9645) User Rights Management SIP issue on MacOS 10.14.x
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-9645 User Rights Management SIP issue on MacOS 10.14.x Change By: Gheorghe Popescu Assignee: Gheorghe Popescu 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-9645) User Rights Management SIP issue on MacOS 10.14.x
Title: Message Title Gheorghe Popescu commented on PUP-9645 Re: User Rights Management SIP issue on MacOS 10.14.x Marshall Taylor i set up an agent with the latest OS X that fixed user management and i was able to run puppet agent -t. Can you provide an example of a manifest that would break the functionality? 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-275) As a end user, the error message for empty string line could be better
Title: Message Title Adam Buxton created an issue Puppet Strings / PDOC-275 As a end user, the error message for empty string line could be better Issue Type: Improvement Assignee: Unassigned Created: 2019/04/17 5:31 AM Priority: Normal Reporter: Adam Buxton if you create a class as follows # classname# @tag# class classname When running `Puppet string generate` a [warn] message is generated. [warn]: Missing documentation for Puppet class 'classname' at manifests/init.pp:linenumber. the error message identifies the line number of the line with no comment or code, and declares it as undocumented Question? does the line really matter at all? if so can the error be clearer 'remove or comment empty lines for reason x' if not can the error be quashed. Add Comment
Jira (PUP-9645) User Rights Management SIP issue on MacOS 10.14.x
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9645 User Rights Management SIP issue on MacOS 10.14.x Change By: Mihai Buzgau Sprint: PR - Triage 2019-05-02 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-9645) User Rights Management SIP issue on MacOS 10.14.x
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9645 User Rights Management SIP issue on MacOS 10.14.x Change By: Mihai Buzgau Story Points: 2 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-9639) Windows package resource does not remove trailing whitespace
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9639 Windows package resource does not remove trailing whitespace Change By: Mihai Buzgau Sprint: PR - Triage 2019-05-02 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-9639) Windows package resource does not remove trailing whitespace
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9639 Windows package resource does not remove trailing whitespace Change By: Mihai Buzgau Story Points: 3 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-9564) Puppet upgrades debian packages with pending updates when setting them on hold
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9564 Puppet upgrades debian packages with pending updates when setting them on hold Change By: Mihai Buzgau Sprint: PR - 2019-04-17 , PR - 2019-05-02 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-1082) pip provider should handle multiple pips/pythons
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-1082 pip provider should handle multiple pips/pythons Change By: Mihai Buzgau Sprint: PR - 2019-04-17 , PR - 2019-05-02 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-8664) rpm package provider is too specific
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-8664 rpm package provider is too specific Change By: Mihai Buzgau Sprint: PR - 2019-04-03, PR - 2019-04-17 , PR - 2019-05-02 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-9502) codesigning puppet executables on macOS 10.14
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9502 codesigning puppet executables on macOS 10.14 Change By: Mihai Buzgau Sprint: PR - 2019-04-17 , PR - 2019-05-02 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-9601) mount resource should trigger 'systemctl daemon-reload'
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9601 mount resource should trigger 'systemctl daemon-reload' Change By: Mihai Buzgau Sprint: PR - 2019-04-17 , PR - 2019-05-02 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-6488) Gem provider should allow alternative gem command; should not rely on $PATH
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-6488 Gem provider should allow alternative gem command; should not rely on $PATH Change By: Mihai Buzgau Sprint: PR - 2019-04-17 , PR - 2019-05-02 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-1888) 'os.release' values not correct for VZ7
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1888 'os.release' values not correct for VZ7 Change By: Mihai Buzgau Sprint: PR - 2019-04-03, PR - 2019-04-17 , PR - 2019-05-02 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-1886) Facter3 should also check for 'Virtuozzo Linux'
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1886 Facter3 should also check for 'Virtuozzo Linux' Change By: Mihai Buzgau Sprint: PR - 2019-04-17 , PR - 2019-05-02 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-3482) server-side only execution stub
Title: Message Title Maximilian Philipps commented on PUP-3482 Re: server-side only execution stub hi, Are there any plans to fix this? I have been trying to write a generate() puppet function for the last few hours only to discover that implementation for Puppet::Util::Execution.execute is highly confusing. For anyone else trying something similar here is what I discovered: Puppet::Util::Exection.execute is the intended way of calling an external program from puppet. This is the case for client side (like a Exec) Resource and for server side (generate()). execute() takes a set of options, however what documented and what is implemented quickly diverges. For example the code sets a default value for suppress_window, the documentation never mentions it and I am not sure it is ever actually used. Presumably that is a MS Windows specific option anyway. Following that we run into several ifs that determine which code path to use for actually executing the command. The first one appears to be used for for spec testing (Puppet::Util::Execution_stub, the second is for POSIX and the last for MS Windows. For Puppet Linux is considered a POSIX system and for client side execution this is the path taken. However on the server things a different. If we try same path as on the client we discover that Kernel.fork is not implemented in JRuby and that the server instead intercepts the execution call through the spec test path and instead continues in Puppet::Server::Execution. Not supported options are just silently dropped. Is there any reason to fall back into the java code for the puppet server? Surely there must be a way to call an external command from JRuby. Even if Kernel.fork is not implemented, maybe there is something like Kernel.spawn? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9573) win32-service gem needs updating
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9573 win32-service gem needs updating Change By: Mihai Buzgau Sprint: PR - Triage 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.
