Jira (FACT-1787) Bump facter version to 3.6.8
Title: Message Title Sean McDonald created an issue Facter / FACT-1787 Bump facter version to 3.6.8 Issue Type: Task Assignee: Branan Riley Created: 2017/10/25 4:17 PM Fix Versions: FACT 3.6.8 Priority: Normal Reporter: Sean McDonald 1) Check that the version number in source for facter is correct version for facter should be 3.6.8 check CMakeLists.txt for the project(FACTER VERSION X.Y.Z) variable check lib/Doxyfile for the PROJECT_NUMBER variable check locales/FACTER.pot for the Project-Id-Version variable Add Comment
Jira (PUP-8093) Bump puppet version to 4.10.9
Title: Message Title Sean McDonald created an issue Puppet / PUP-8093 Bump puppet version to 4.10.9 Issue Type: Task Assignee: Branan Riley Created: 2017/10/25 4:17 PM Fix Versions: PUP 4.10.9 Priority: Normal Reporter: Sean McDonald 1) Check that the version number in source for puppet is correct version for puppet should be 4.10.9 check lib/puppet/version.rb for the PUPPETVERSION variable check .gemspec for version variable Add Comment
Jira (PDB-3734) Ensure that resource indirection uses existing resource type
Title: Message Title Russell Mull commented on PDB-3734 Re: Ensure that resource indirection uses existing resource type Does this solve an issue we've seen there? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8029) Concatenated strings causing breakages with Japanese
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8029
Concatenated strings causing breakages with Japanese
Change By:
Eric Delaney
Comment:
{code}[centos@ericdelaney puppet]$ find lib -type f -print | xargs grep '_(' | grep '+'lib/puppet/face/epp.rb:raise Puppet::Error, _("One or more file(s) specified did not exist:\n") + missing_files.map { |f| " #{f}" }.join("\n")lib/puppet/face/epp.rb: raise Puppet::Error, _("One or more file(s) specified did not exist:\n") + missing_files.collect { |f| " #{f}" }.join("\n")lib/puppet/face/help.rb: summary = face.deprecated? ? face.summary + _(" (Deprecated)") : face.summarylib/puppet/face/module/build.rb: _("Module built: ") + return_value.expand_path.to_slib/puppet/face/module/list.rb:str << ' ' + colorize(:red, _('invalid'))lib/puppet/face/module/list.rb: str << ' ' + colorize(:red, _('invalid'))lib/puppet/face/parser.rb:raise Puppet::Error, _("One or more file(s) specified did not exist:\n%{files}") % { files: missing_files.collect {|f| " " * 3 + f + "\n"} }lib/puppet/face/parser.rb: dumps + _("One or more file(s) specified did not exist:\n") + missing_files.collect { |f| " #{f}" }.join("\n")lib/puppet/functions/slice.rb: raise ArgumentError, _("slice(): block must define one parameter, or ") +lib/puppet/functions/slice.rb:_("the same number of parameters as the given size of the slice (%{slice_size}). Block has %{serving_size}; ") % { slice_size: slice_size, serving_size: serving_size }+lib/puppet/graph/simple_graph.rb: message += _("Cycle graph written to %{filename}.") % { filename: filename }lib/puppet/graph/simple_graph.rb: message += _("Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz")lib/puppet/module_tool/errors/shared.rb: trace += @source[1..-1].map { |m| _("which depends on '%{name}' (%{version})") % { name: m[:name], version: v(m[:version]) } }lib/puppet/network/http/error.rb: super(_("Not Acceptable: ") + message, CODE, issue_kind)lib/puppet/network/http/error.rb: super(_("Not Found: ") + message, CODE, issue_kind)lib/puppet/network/http/error.rb: super(_("Not Authorized: ") + message, CODE, issue_kind)lib/puppet/network/http/error.rb: super(_("Bad Request: ") + message, CODE, issue_kind)lib/puppet/network/http/error.rb: super(_("Method Not Allowed: ") + message, CODE, issue_kind)lib/puppet/network/http/error.rb: super(_("Unsupported Media Type: ") + message, CODE, issue_kind)lib/puppet/network/http/error.rb: super(_("Server Error: ") + original_error.message, CODE, issue_kind)lib/puppet/parameter/value_collection.rb: str += _("Valid values are %{value_list}. ") % { value_list: values.join(", ") } unless values.empty?lib/puppet/parameter/value_collection.rb: str += _("Valid values match %{pattern}.") % { pattern: regexes.join(", ") } unless regexes.empty?lib/puppet/pops/lookup/lookup_adapter.rb:msg += _(". A '%{config}' file should be used instead") % { config: HieraConfig::CONFIG_FILE_NAME } if mp.nil?lib/puppet/pops/lookup/lookup_adapter.rb:_("Defining environment_data_provider='%{provider_name}' in environment.conf is deprecated") % { provider_name: provider_name }, env_path +
Jira (PUP-8029) Concatenated strings causing breakages with Japanese
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8029
Concatenated strings causing breakages with Japanese
Change By:
Eric Delaney
Comment:
{code} [centos@ericdelaney lib]$ find . -type f -print | xargs grep '+= _'./puppet/graph/simple_graph.rb: message += _("Cycle graph written to %{filename}.") % { filename: filename }./puppet/graph/simple_graph.rb: message += _("Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz")./puppet/parameter/value_collection.rb: str += _("Valid values are %{value_list}. ") % { value_list: values.join(", ") } unless values.empty?./puppet/parameter/value_collection.rb: str += _("Valid values match %{pattern}.") % { pattern: regexes.join(", ") } unless regexes.empty?./puppet/pops/lookup/lookup_adapter.rb:msg += _(". A '%{config}' file should be used instead") % { config: HieraConfig::CONFIG_FILE_NAME } if mp.nil?./puppet/pops/lookup/lookup_adapter.rb:msg += _(". A '%{config}' file should be used instead") % { config: HieraConfig::CONFIG_FILE_NAME } if ep.nil?[centos@ericdelaney lib]${code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-8029) Concatenated strings causing breakages with Japanese
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8029
Concatenated strings causing breakages with Japanese
Change By:
Eric Delaney
Comment:
{code}/puppet/syntax_checkers/base64.rb if (cleaned_text.bytes.to_a.size * 8) % 6 != 0msg2 = _("padding is not correct") elsemsg2 = _("contains letters outside strict base 64 range (or whitespace)") end msg = _("Base64 syntax checker: Cannot parse invalid Base64 string - %{msg2}") % { msg2: msg2 }{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-8029) Concatenated strings causing breakages with Japanese
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8029
Concatenated strings causing breakages with Japanese
Change By:
Eric Delaney
Comment:
{code}[centos@ericdelaney puppet]$ find lib -type f -print | xargs grep '_(' | grep '<<'lib/puppet/face/module/uninstall.rb: Puppet.notice _("Preparing to uninstall '%{name}'") % { name: name } << (options[:version] ? " (#{colorize(:cyan, options[:version].sub(/^(?=\d)/, 'v'))})" : '') << " ..."lib/puppet/face/module/list.rb:str << ' ' + colorize(:red, _('invalid'))lib/puppet/face/module/list.rb: str << ' ' + colorize(:red, _('invalid'))lib/puppet/forge/errors.rb: message = _(<<-EOS).chomp % { uri: @uri, response: @response }lib/puppet/forge/errors.rb: message << _("\n The message we received said '%{message}'") % { message: @message } if @messagelib/puppet/module_tool/errors/installer.rb: message << _("Could not install module '%{module_name}' (%{version})") % { module_name: @module_name, version: @requested_version }lib/puppet/module_tool/errors/installer.rb: message << _(" Module '%{module_name}' (%{version}) is already installed") % { module_name: @module_name, version: @installed_version }lib/puppet/module_tool/errors/installer.rb: message << _("Installed module has had changes made locally") unless @local_changes.empty?lib/puppet/module_tool/errors/installer.rb: message << _("Use `puppet module upgrade` to install a different version")lib/puppet/module_tool/errors/installer.rb: message << _("Use `puppet module install --force` to re-install only this module")lib/puppet/module_tool/errors/installer.rb: message << _("Could not install '%{requested_package}'") % { requested_package: @requested_package }lib/puppet/module_tool/errors/installer.rb: message << _(" No releases are available from %{source}") % { source: @source }lib/puppet/module_tool/errors/installer.rb: message << _("Does '%{requested_package}' have at least one published release?") % { requested_package: @requested_package }lib/puppet/module_tool/errors/shared.rb: message << _("Could not %{action} module '%{module_name}' (%{version})") % { action: @action, module_name: @requested_name, version: vstring }lib/puppet/module_tool/errors/shared.rb: message << _(" No version of '%{module_name}' can satisfy all dependencies") % { module_name: @requested_name }lib/puppet/module_tool/errors/shared.rb: message << _("Use `puppet module %{action} --ignore-dependencies` to %{action} only this module") % { action: @action }lib/puppet/module_tool/errors/shared.rb: message << _("Could not %{action} '%{module_name}' (%{version})") % { action: @action, module_name: @module_name, version: vstring }lib/puppet/module_tool/errors/shared.rb:message << _(" No releases are available from %{source}") % { source: @source }lib/puppet/module_tool/errors/shared.rb:message << _("Does '%{module_name}' have at least one published release?") % { module_name: @module_name }lib/puppet/module_tool/errors/shared.rb:message << _(" No releases matching '%{version}' are available from %{source}") % { version: @requested_version, source: @source }lib/puppet/module_tool/errors/shared.rb: message << _("Could not install module '%{module_name}' (%{version})") % { module_name:
Jira (PUP-8092) Concatenated strings causing breakages with Japanese group 2
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8092
Concatenated strings causing breakages with Japanese group 2
Change By:
Eric Delaney
There are some concatenated strings in Puppet that are resulting in mistranslations because the translator doesn't have the full context of what the complete sentence is supposed to be, and cannot change the sentence order, Example {code} [centos@ericdelaney lib]$ find . -type f -print | xargs grep '+= _'./puppet/graph/simple_graph.rb : message += _("Cycle graph written to %{filename}.") % { filename: filename } https ./puppet/graph/simple_graph.rb : message += _("Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz"). / puppet / github parameter/value_collection . com rb: str += _("Valid values are %{value_list}. ") % { value_list: values.join(", ") } unless values.empty?. / puppetlabs puppet / parameter/value_collection.rb: str += _("Valid values match %{pattern}.") % { pattern: regexes.join(", ") } unless regexes.empty?./ puppet/ blob pops / master lookup / lookup_adapter.rb:msg += _(". A '%{config}' file should be used instead") % { config: HieraConfig::CONFIG_FILE_NAME } if mp.nil?./puppet/pops/lookup/lookup_adapter.rb:msg += _(". A '%{config}' file should be used instead") % { config: HieraConfig::CONFIG_FILE_NAME } if ep.nil?[centos@ericdelaney lib ]${code}{code}[centos@ericdelaney puppet]$ find lib -type f -print | xargs grep '_(' | grep '+'lib /puppet/ indirector face / catalog epp.rb:raise Puppet::Error, _("One or more file(s) specified did not exist:\n") + missing_files.map { |f| " #{f}" }.join("\n")lib / compiler puppet/face/epp .rb : raise Puppet::Error, _("One or more file(s) specified did not exist:\n") + missing_files.collect { |f| " # L273 {f}" }.join("\n")lib/puppet/face/help.rb: summary = face.deprecated? ? face.summary + _(" (Deprecated)") : face.summarylib/puppet/face/module/build.rb: _("Module built: ") + return_value.expand_path.to_slib/puppet/face/module/list.rb:str << ' ' + colorize(:red, _('invalid'))lib/puppet/face/module/list.rb: str << ' ' + colorize(:red, _('invalid'))lib/puppet/face/parser.rb:raise Puppet::Error, _("One or more file(s) specified did not exist:\n%{files}") % { files: missing_files.collect {|f| " " * 3 + f + "\n"} }lib/puppet/face/parser.rb: dumps + _("One or more file(s) specified did not exist:\n") + missing_files.collect { |f| " #{f}" }.join("\n")lib/puppet/functions/slice.rb: raise ArgumentError, _("slice(): block must define one parameter, or ") +lib/puppet/functions/slice.rb:_("the same number of parameters as the given size of the slice (%{slice_size}). Block has %{serving_size}; ") % { slice_size: slice_size, serving_size: serving_size }+lib/puppet/graph/simple_graph.rb: message += _("Cycle graph written to %{filename}.") % { filename: filename }lib/puppet/graph/simple_graph.rb: message += _("Try the ' - L276 -graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz") https lib/puppet/module_tool/errors/shared.rb : trace += @source[1..-1].map { |m| _("which depends on '%{name}' (%{version})") % { name: m[:name], version: v(m[:version]) } }lib /
Jira (PUP-8092) Concatenated strings causing breakages with Japanese group 2
Title: Message Title Larissa Lane created an issue Puppet / PUP-8092 Concatenated strings causing breakages with Japanese group 2 Issue Type: Bug Assignee: Eric Delaney Created: 2017/10/25 4:01 PM Fix Versions: PUP 5.3.3 Labels: i18n Priority: Normal Reporter: Larissa Lane There are some concatenated strings in Puppet that are resulting in mistranslations because the translator doesn't have the full context of what the complete sentence is supposed to be, and cannot change the sentence order, Example: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/indirector/catalog/compiler.rb#L273-L276 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/indirector/catalog/compiler.rb#L291-L292 These might be the only two occurrences Eric Delaney
Jira (PUP-8029) Concatenated strings causing breakages with Japanese
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8029 Concatenated strings causing breakages with Japanese Change By: Eric Delaney Fix Version/s: PUP 5.3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-122) Support multiple module directories in the path
Title: Message Title Jean Bond updated an issue Puppet Task Runner / BOLT-122 Support multiple module directories in the path Change By: Jean Bond Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8008 puppet module install fails to install apt 4.2.0 Change By: Ethan Brown Fix Version/s: PUP 5.3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8083) NTFS reparse points return invalid path data strings for mount points (like those in a DFS share)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8083 NTFS reparse points return invalid path data strings for mount points (like those in a DFS share) Change By: Ethan Brown Fix Version/s: PUP 5.3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Michael Smith updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Michael Smith Fix Version/s: PUP 4.10.9 Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Michael Smith commented on PUP-2169 Re: Not possible to manage SELinux file contexts via puppet in a sane way Due to the performance regression, we've decided to revert this change for now and not include it in the pending release. Fixes that resolve the issue on RedHat 5 and 6 would be very welcome. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1786) Bump facter version to 3.9.3
Title: Message Title Geoff Nichols created an issue Facter / FACT-1786 Bump facter version to 3.9.3 Issue Type: Task Assignee: Enis Inan Created: 2017/10/25 2:31 PM Fix Versions: FACT 3.9.3 Priority: Normal Reporter: Geoff Nichols 1) Check that the version number in source for facter is correct version for facter should be 3.9.3 check CMakeLists.txt for the project(FACTER VERSION X.Y.Z) variable check lib/Doxyfile for the PROJECT_NUMBER variable check locales/FACTER.pot for the Project-Id-Version variable Add Comment
Jira (PUP-8091) Bump puppet version to 5.3.3
Title: Message Title Geoff Nichols created an issue Puppet / PUP-8091 Bump puppet version to 5.3.3 Issue Type: Task Assignee: Enis Inan Created: 2017/10/25 2:31 PM Fix Versions: PUP 5.3.3 Priority: Normal Reporter: Geoff Nichols 1) Check that the version number in source for puppet is correct version for puppet should be 5.3.3 check lib/puppet/version.rb for the PUPPETVERSION variable check .gemspec for version variable Add Comment
Jira (PDB-3737) (maint) update 5.1.2 release notes
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3737 (maint) update 5.1.2 release notes Issue Type: Bug Assignee: Unassigned Created: 2017/10/25 1:56 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-5518) Puppet lookup: document precedence of mixed styles of defaults
Title: Message Title Claire Cadman commented on PUP-5518 Re: Puppet lookup: document precedence of mixed styles of defaults Henrik Lindberg Sure! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3736) (maint) update 5.1.2 release notes
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3736 (maint) update 5.1.2 release notes Issue Type: Bug Assignee: Unassigned Created: 2017/10/25 1:16 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (BOLT-52) Pass arguments to scripts
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-52 Pass arguments to scripts Change By: Josh Cooper Sprint: Tasks ELP Kanban Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Michael Smith commented on PUP-2169 Re: Not possible to manage SELinux file contexts via puppet in a sane way This seems to have introduced a serious performance regression in our test environments on Redhat 5 and 6 (but not 7). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-44) Display human-readable results from running a task
Title: Message Title Jenny Mahmoudi commented on BOLT-44 Re: Display human-readable results from running a task Josh Cooper Patrick Carlisle Any questions on the spec as we left it before PuppetConf? https://github.com/puppetlabs/bolt/blob/master/ux/bolt-CLI-spec.md Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3733) PDB 5.1.2 Release
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3733 PDB 5.1.2 Release Change By: Zachary Kent Resolution: Done Assignee: Zachary Kent Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3630) Configurable facts blacklist
Title: Message Title Russell Mull commented on PDB-3630 Re: Configurable facts blacklist It should get flushed the next time a factset comes in for that node. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3630) Configurable facts blacklist
Title: Message Title Nick Walker commented on PDB-3630 Re: Configurable facts blacklist Zachary Kent Russell Mull What is the behavior of PuppetDB when a fact is already being stored and then is added to the blacklist? Will that fact be deleted from the database or will it stick around and just no longer receive updates? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8090) Load module translation files
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8090 Load module translation files Change By: Maggie Dreyer Acceptance Criteria: Module translations show up during an agent run _and_ when using puppet's CLI applications. Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8089) Pluginsync locale files
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8089
Pluginsync locale files
Change By:
Maggie Dreyer
The first part of getting module translations visible on the the agent is to actually download the locale files along with the other module data. This involves the following steps:- Add a new mount in [file_serving/mount|https://github.com/puppetlabs/puppet/tree/master/lib/puppet/file_serving/mount] to find locale files in modules on the master.- Add a new Downloader to the [DownloaderFactory|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/configurer/downloader_factory.rb] for downloading locale files. This downloader should put the files into a directory structure like {{$vardir/locales//.po}}. For the time being, we should sync all of the available locales, not just the one detected on the system. This can be optimized later if needed.- Add the relevant settings for the new downloader (e.g. {{localedest}} and {{localesource}}) to the [settings defaults|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/defaults.rb #L1690-L1729 ].- Add tests for the new Downloader to the [downloader factor specs|https://github.com/puppetlabs/puppet/blob/master/spec/unit/configurer/downloader_factory_spec.rb].- Update the tests in the [plugin handler specs|https://github.com/puppetlabs/puppet/blob/master/spec/unit/configurer/plugin_handler_spec.rb] to exercise the locale downloader.Other pieces may fall out of this, and other tests may need to be updated, but this is a good start. Note that this will not cause any module translations to actually be displayed; this ticket's other subtask describes the work needed to load the translation files from {{$vardir}} once they are present.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8090) Load module translation files
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-8090 Load module translation files Issue Type: Sub-task Assignee: Unassigned Created: 2017/10/25 11:06 AM Priority: Normal Reporter: Maggie Dreyer Currently we are naively loading modules' translations whenever a Ruby instance of the Module class is created, in a way assumes that the locale files are located within the module's installed directory. This works on the master and when doing things like puppet apply, but agent runs get their data from $vardir, which is populated by pluginsync. We need to add hooks to load module translations from $vardir after pluginsyncing, and make sure we check both places (installed modules and $vardir) when invoking puppet applications, to ensure we get translations when and where we need them. This ticket mostly entails getting correct translation behavior, over optimizing, which is covered in PUP-8024. Add Comment
Jira (PUP-8089) Pluginsync locale files
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-8089 Pluginsync locale files Issue Type: Sub-task Assignee: Unassigned Created: 2017/10/25 10:58 AM Priority: Normal Reporter: Maggie Dreyer The first part of getting module translations visible on the the agent is to actually download the locale files along with the other module data. This involves the following steps: Add a new mount in file_serving/mount to find locale files in modules on the master. Add a new Downloader to the DownloaderFactory for downloading locale files. This downloader should put the files into a directory structure like $vardir/locales//.po. For the time being, we should sync all of the available locales, not just the one detected on the system. This can be optimized later if needed. Add the relevant settings for the new downloader (e.g. localedest and localesource) to the settings defaults. Add tests for the new Downloader to the downloader factor specs. Update the tests in the plugin handler specs to exercise the locale downloader. Other pieces may fall out of this, and other tests may need to be updated, but this is a good
Jira (PUP-7517) Add logic for restarting hung catalog application
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7517 Add logic for restarting hung catalog application Change By: Kenn Hussey Fix Version/s: PUP 4.10.9 Fix Version/s: PUP 4.10.10 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7517) Add logic for restarting hung catalog application
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7517 Add logic for restarting hung catalog application Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8083) NTFS reparse points return invalid path data strings for mount points (like those in a DFS share)
Title: Message Title Kenn Hussey commented on PUP-8083 Re: NTFS reparse points return invalid path data strings for mount points (like those in a DFS share) Ethan Brown I assume this needs a 5.3.3 fix version too? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3735) (maint) Update version to 1.2.2
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3735 (maint) Update version to 1.2.2 Issue Type: Bug Assignee: Unassigned Created: 2017/10/25 10:01 AM Priority: Normal Reporter: gepetto-bot Version 1.2.1 was previously released reporting 1.3.0. The actual changes were only bug fixes, so continuing in the 1.2 line with 1.2.2. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (BOLT-45) Display JSON results
Title: Message Title
Alex Dreyer commented on BOLT-45
Re: Display JSON results
There is no such spec or schema yet.
[alex@orch-next ~]$ puppet-task run echo message="output" -q 'nodes[certname] { certname ~ "boron" }' --format=json
{
"job_name": "2876",
"command": "task",
"options": {"noop":false,"task":"echo","scope":{"query":"nodes[certname] { certname ~ \"boron\" }"},"params":{"message":"output"},"transport":"pxp","description":"","environment":"production"},
"owner": "alex",
"start_timestamp": "2017-10-25T16:47:07Z",
"items": [
{"name": "boron-1", "state": "finished", "results": {"message":"output"}}
,
Jira (BOLT-196) Allow multiple nodes options
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-196 Allow multiple nodes options Change By: Josh Cooper Sprint: Tasks ELP Kanban Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-45) Display JSON results
Title: Message Title Josh Cooper commented on BOLT-45 Re: Display JSON results Alex Dreyer can you point me to the json output spec or schema? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-163) Configurable connection timeout
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-163 Configurable connection timeout Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-161) Display error messages from tasks
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-161 Display error messages from tasks Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-169) Execution results for tasks that did not output JSON are not hashes
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-169 Execution results for tasks that did not output JSON are not hashes Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-158) Bolt should run .pp tasks with puppet on windows
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-158 Bolt should run .pp tasks with puppet on windows Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-160) The bolt task run should handle _output specially
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-160 The bolt task run should handle _output specially Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3734) Ensure that resource indirection uses existing resource type
Title: Message Title Thomas Hallgren assigned an issue to Unassigned PuppetDB / PDB-3734 Ensure that resource indirection uses existing resource type Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8025) `puppet module install` does not correctly install locale files
Title: Message Title Michael Smith updated an issue Puppet / PUP-8025 `puppet module install` does not correctly install locale files Change By: Michael Smith Fix Version/s: PUP 5.3.3 Fix Version/s: PUP 5.3.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8025) `puppet module install` does not correctly install locale files
Title: Message Title Kenn Hussey commented on PUP-8025 Re: `puppet module install` does not correctly install locale files Eric Putnam this should perhaps be targeted for 5.3.4 (or even 5.3.z), as it won't make the cut-off for 5.3.3. /cc Craig Gomes Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3734) Ensure that resource indirection uses existing resource type
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren PuppetDB / PDB-3734 Ensure that resource indirection uses existing resource type Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3734) Ensure that resource indirection uses existing resource type
Title: Message Title Thomas Hallgren created an issue PuppetDB / PDB-3734 Ensure that resource indirection uses existing resource type Issue Type: Bug Assignee: Unassigned Created: 2017/10/25 9:05 AM Priority: Normal Reporter: Thomas Hallgren The Puppet::Resource::Puppetdb#search method creates a new Resource by passing the resource type in string format. This is problematic since that string might be resolved by loading a Ruby resource type. This is a potential source of conflicts when puppet generate types is used and the root cause of the error reported in PUP-8002. In other places of puppet the code is changed to instead load the resource type using the Puppet::Pops::Evaluator::Runtime3ResourceSupport#find_resource_type method, thus preventing the Ruby type from being loaded. Add Comment
Jira (PUP-7517) Add logic for restarting hung catalog application
Title: Message Title Kenn Hussey commented on PUP-7517 Re: Add logic for restarting hung catalog application Charlie Sharpsteen Justin Stoller the deadline for getting this into Puppet 4.10.9 was effectively yesterday; are you still working to get this into the release? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8026) Module code translation should be supported with puppet agent runs
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8026 Module code translation should be supported with puppet agent runs Change By: Maggie Dreyer Sprint: Platform Core Grooming KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-146) Configure what interpreter/shell to use
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-146 Configure what interpreter/shell to use Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8026) Module code translation should be supported with puppet agent runs
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-8026 Module code translation should be supported with puppet agent runs Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-125) Support WinRM over SSL
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-125 Support WinRM over SSL Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-118) Oneline output format
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-118 Oneline output format Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-156) implement powershell input method
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-156 implement powershell input method Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-190) Tasks in subfolders of a module are not found
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-190 Tasks in subfolders of a module are not found Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-169) Execution results for tasks that did not output JSON are not hashes
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-169
Execution results for tasks that did not output JSON are not hashes
Change By:
Alex Dreyer
Bolt should be wrapping string output in a json object or hash instead the execution result just contains the string. This breaks functions that process execution results. Currently if you execute a task that does not return a JSON object the execution result value is a string not JSON object. Bolt should be wrapping the result in a JSON object so it's easier to use in plans and matches the orchestrator result { code}Task output:[1, 2, 3,]Incorrect current behaviorExecutionResult({'vagrant' => " [1, 2, 3,]\n"})Correct behavior:ExecutionResult({'vagrant' => {" _output": ""} }){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-169) Execution results for tasks that did not output JSON are not hashes
Title: Message Title
Josh Cooper commented on BOLT-169
Re: Execution results for tasks that did not output JSON are not hashes
Currently, given the sample::stdin task:
#!/bin/bash
grep "message"
We generate:
bundle exec bolt task run sample::stdin -n qoyqlzramcgist1.delivery.puppetlabs.net -k --modulepath spec/fixtures/modules message=hello
qoyqlzramcgist1.delivery.puppetlabs.net:
{"message":"hello"}
Jira (PUP-8078) Make it possible to create parameterized Object data types
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8078 Make it possible to create parameterized Object data types Change By: Thomas Hallgren Story Points: 3 5 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-161) Display error messages from tasks
Title: Message Title Alex Dreyer commented on BOLT-161 Re: Display error messages from tasks This applies primarily to task run now. When we improve logging for tasks that run as part of a plan it should apply to that too. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-196) Allow multiple nodes options
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-196 Allow multiple nodes options Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8078) Make it possible to create parameterized Object data types
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8078 Make it possible to create parameterized Object data types Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8078) Make it possible to create parameterized Object data types
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-8078 Make it possible to create parameterized Object data types Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8078) Make it possible to create parameterized Object data types
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8078 Make it possible to create parameterized Object data types Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8087) hiera acceptance tests fail with permission denied on hiera_config directory
Title: Message Title John Duarte updated an issue Puppet / PUP-8087 hiera acceptance tests fail with permission denied on hiera_config directory Change By: John Duarte QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8086) Provide PAL API to use a modulepath and environment name
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8086 Provide PAL API to use a modulepath and environment name Change By: Josh Cooper Sprint: Tasks ELP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8087) hiera acceptance tests fail with permission denied on hiera_config directory
Title: Message Title John Duarte updated an issue Puppet / PUP-8087 hiera acceptance tests fail with permission denied on hiera_config directory Change By: John Duarte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8087) hiera acceptance tests fail with permission denied on hiera_config directory
Title: Message Title John Duarte assigned an issue to Unassigned Puppet / PUP-8087 hiera acceptance tests fail with permission denied on hiera_config directory Change By: John Duarte Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8087) hiera acceptance tests fail with permission denied on hiera_config directory
Title: Message Title John Duarte commented on PUP-8087 Re: hiera acceptance tests fail with permission denied on hiera_config directory Revert merged into 5.3.x at https://github.com/puppetlabs/puppet/commit/9cf816f49fb3fbd9342aab5b93f6a43e7fa93ea8 Latest passing puppet-agent 5.3.x Last known good build of puppet-agent on 5.3.x: Built at: 25 Oct 2017 0:05:57 PUPPET_AGENT_VERSION: 5.3.2.100.g92ab84c PUPPET_AGENT_COMMIT: 92ab84c1899bb9c896a52ca176c88a9e8539af29 PUPPET_AGENT_SHORT_COMMIT: 92ab84c18 FACTER_COMMIT: a73772b0fd33fa8d24d389aff074b00034dd318d PUPPET_COMMIT: 9cf816f49fb3fbd9342aab5b93f6a43e7fa93ea8 HIERA_COMMIT: refs/tags/3.4.2 PXPAGENT_COMMIT: 44a3c32e549982dd75738430fb9d382d6245f0b8
Jira (PUP-3323) yum provider should be able to install from remote URLs
Title: Message Title Eric Delaney updated an issue Puppet / PUP-3323 yum provider should be able to install from remote URLs Change By: Eric Delaney QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8083) NTFS reparse points return invalid path data strings for mount points (like those in a DFS share)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8083 NTFS reparse points return invalid path data strings for mount points (like those in a DFS share) Change By: Ethan Brown Fix Version/s: PUP 4.10.9 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8083) NTFS reparse points return invalid path data strings for mount points (like those in a DFS share)
Title: Message Title Ethan Brown commented on PUP-8083 Re: NTFS reparse points return invalid path data strings for mount points (like those in a DFS share) Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/6c64bebe49a6c6b5a4c6eb5c7bf1ef8bb3d2137a Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8084) Hiera lookup failed when using serialized regex in yaml
Title: Message Title
Olivier Hanesse commented on PUP-8084
Re: Hiera lookup failed when using serialized regex in yaml
Thanks for your answer. In fact, explicit lookup didn't work either.
The aim of having a regexp in "hiera yaml" was to generate a yaml file from that hash that need to get regexp as key (searchguard plugin configuration for elasticsearch) To do that, I was using a function with a "hash.to_yaml"
Now in Hiera, I put a string like ''!ruby/regexp ^foo-\S*' , and I wrote to function to get a real regexp in my hash before converting it to a yaml file.
def transform_regexpkeys_to_regexp(value)
return value if not value.is_a?(Hash)
hash = value.inject({}) { |memo,(k,v)|
memo[k.start_with?('!ruby/regexp') ? Regexp.new(k.gsub(/!ruby\/regexp /,'')) : k] = transform_regexpkeys_to_regexp(v); memo
}
return hash
end
And I got the same yaml output as with earlier Puppet version Maybe I could write this function using Puppet Language only
Jira (PUP-8084) Hiera lookup failed when using serialized regex in yaml
Title: Message Title Henrik Lindberg commented on PUP-8084 Re: Hiera lookup failed when using serialized regex in yaml You could also use APL but get the value as a string. You can then transform the string to a Regexp (i.e. Regexp($strval). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-57) Download a file
Title: Message Title Henrik Lindberg commented on BOLT-57 Re: Download a file Auto cleanup sounds good. A user that wants to keep a file could always run a "copy file" local task to persiste the file past the end of the plan. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-589) Using %{scope()} function converts any variable to a string with no way to override
Title: Message Title
Henrik Lindberg commented on HI-589
Re: Using %{scope()} function converts any variable to a string with no way to override
This is by design. We have a ticket PUP-7675 about adding the ability to typecast a result - (as a simple example this could turn a string "true" into a boolean true value). That is however not a full solution as it is difficult to deal with values that have structure (array's and hashes) this way.
There is also the hiera interpolation function alias, which, if used as the only thing in a string will return the aliased key verbatim (without turning it into a string). This may however not be applicable in your case since you want the value of a variable. To make this work you would make the variable that you want to reference also set from hiera, and you can then lookup that value via the alias interpolation function instead of using scope.
In hiera 5, you can easily write your own custom backend functions and you are then free to do what you want - for example; lookup up variables, transform them etc. You can even write such functions in the puppet language.
We are not likely to change how the hiera scope interpolation function works because of the consequences this has on backwards compatibility.
Closing this as won't do as there are other ways to achieve what you want.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-8086) Provide PAL API to use a modulepath and environment name
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-8086 Provide PAL API to use a modulepath and environment name Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Henrik Lindberg commented on PUP-7629 Re: Hieradata should be loaded and cached in accordance with the environment_timeout Another issue here is that non file based backends have no way (in general) of "snapshotting" data - thus data in a DB backend may change at any time. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7531) give user control over optional/strict in hiera interpolation
Title: Message Title Henrik Lindberg commented on PUP-7531 Re: give user control over optional/strict in hiera interpolation Ping Eric Sorenson - this needs product / Ux love - should we help with the problems described and work on the suggested solution? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7508) Failing mapped_paths don't get explained by lookup --explain
Title: Message Title Henrik Lindberg commented on PUP-7508 Re: Failing mapped_paths don't get explained by lookup --explain Ping Eric Sorenson - needs some product/Ux love - suggestions above; how should we do this in a good way? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7507) puppet lookup --facts can't modify $facts hash
Title: Message Title Henrik Lindberg commented on PUP-7507 Re: puppet lookup --facts can't modify $facts hash A unit or acceptance test that shows the problems (or that asserts that they are fixed?) would be great. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5518) Puppet lookup: document precedence of mixed styles of defaults
Title: Message Title Henrik Lindberg commented on PUP-5518 Re: Puppet lookup: document precedence of mixed styles of defaults Ping Claire Cadman want this as a docs ticket for the hiera 5 documentation? Please take it Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5518) Puppet lookup: document precedence of mixed styles of defaults
Title: Message Title Henrik Lindberg assigned an issue to Claire Cadman Puppet / PUP-5518 Puppet lookup: document precedence of mixed styles of defaults Change By: Henrik Lindberg Assignee: Claire Cadman Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5518) Puppet lookup: Decide whether you can mix styles of defaults or not
Title: Message Title Henrik Lindberg commented on PUP-5518 Re: Puppet lookup: Decide whether you can mix styles of defaults or not We should document that giving a hash of options containing default_value at the same time as giving a lambda means that the lambda will win. (We cannot change this easily as it would be a breaking change). The rationale for allowing this (albeit of limited value) is that you may be using the same hash of options multiple times and some of the calls to lookup you want to override the production of the default value. A default_values_hash should work and there should be tests. This is now only a documentation ticket (make sure that this is documented). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5518) Puppet lookup: document precedence of mixed styles of defaults
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5518 Puppet lookup: document precedence of mixed styles of defaults Change By: Henrik Lindberg Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5518) Puppet lookup: document precedence of mixed styles of defaults
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5518 Puppet lookup: document precedence of mixed styles of defaults Change By: Henrik Lindberg Summary: Puppet lookup: Decide whether you can mix document precedence of mixed styles of defaults or not Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8088) add mechanism for cache eviction callback / finalizers
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8088 add mechanism for cache eviction callback / finalizers Issue Type: Improvement Assignee: Unassigned Created: 2017/10/25 3:35 AM Priority: Normal Reporter: Henrik Lindberg For an advanced hiera backends that open connections to a remote service it is not enough to simply throw away cached information as this may "leak connections". Just waiting for a GC to kick in and then expecting that it clears up a connection is not reliable and it may take a long time before such resources are freed. Depending on the implementation it may not even be freed until the ruby runtime is terminated. The most natural would be to register a callback for a LookupContext cached key (or all keys). Using a lambda for this is however somewhat problematic if the backend is written in the Puppet Language as the lambda does not have access to the local scope it is defined in. It will work if the lookup context instance is given to it and if we document that this lambda only has access to the global scope + the lookup context given to it. Preferably we would make a new implementation of Scope (that is not stupid), but that is a big thing. Alternatives would be to register a named function that gets called with the lookup_context, or using name convention such that mymodule::mybackend::on_evict(lookupcontext) gets called. Neither is very nice. In addition to being able to set the on-eviction-lambda there must be a way to get the already set lambda (to avoid setting it again). Suggest using on_evict() for setting it and on_evict() for getting it, and where on_evict(false) would drop the registered lambda.
Jira (HI-589) Using %{scope()} function converts any variable to a string with no way to override
Title: Message Title
Russell Knighton created an issue
Hiera / HI-589
Using %{scope()} function converts any variable to a string with no way to override
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/10/25 2:12 AM
Priority:
Normal
Reporter:
Russell Knighton
When trying to use the hiera scope interpolation function, everything automatically becomes a String data type. This is, I presume, because we have to wrap %{} in quotes. (Though I have tried without quotes, by escaping the % instead, but though seems to parse correctly, I don't think it functions.)
This means I can not currently look-up a scope defined integer to dynamically pass as a class parameter. (There's other ways to do that, I know, but to be able to use scope() in hiera would be the best way for me in this particular situation.)
Can we have a way to override the datatype of a hiera value?
Add Comment
