Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title Fabien Wernli commented on PUP-9993 Re: lookup's knockout_prefix cannot be undef, contrary to the documentation Here's what I found using the puppetlabs docs search interface: https://puppet.com/docs/puppet/latest/hiera_merging.html : "'knockout_prefix' - string or undef; default is undef" "'knockout_prefix' (String or undef) - Use with a string prefix to indicate a value to remove from the final result. Defaults to undef, which turns off this option." https://puppet.com/docs/puppet/6.4/hiera_merging.html (same as above) https://puppet.com/docs/puppet/5.5/hiera_merging.html (same as above) So this is still in the latest documentation 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323217.1567511185000.12273.1578315900212%40Atlassian.JIRA.
Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title Fabien Wernli commented on PUP-9993 Re: lookup's knockout_prefix cannot be undef, contrary to the documentation My initial use-case was to parameterize a class with `$knockout_prefix` and `undef` would disable it. Of course I can use a switch to enable/disable it, but this is still either a bug or a docbug. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323217.1567511185000.86391.1567666560385%40Atlassian.JIRA.
Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title
Fabien Wernli created an issue
Puppet / PUP-9993
lookup's knockout_prefix cannot be undef, contrary to the documentation
Issue Type:
Bug
Affects Versions:
PUP 6.7.0
Assignee:
Unassigned
Components:
Hiera & Lookup
Created:
2019/09/03 4:46 AM
Priority:
Normal
Reporter:
Fabien Wernli
Puppet Version: 6.7.0 Puppet Server Version: N/A OS Name/Version: Debian Buster The documentation states at various places (e.g. https://puppet.com/docs/puppet/5.2/hiera_use_function.html) that lookup's knockout_prefix parameter is either a string or undef. However, when running puppet apply on the following code, we get an error: lookup( { 'name' => 'foobar', 'value_type' => Hash, 'merge' => { 'strategy' => 'deep', 'knockout_prefix' => undef, } , 'default_value' => {}, }, ) Error: Evaluation Error: Error while evaluating a Function Call, 'lookup' expects one of: (NameType = Variant[String, Array[String]] name, ValueType = Type value_type?, MergeType = Variant[String[1], Hash[String, Scalar]] merge?) rejected: parameter 'name' expects a NameType = Variant[String, Array[String]] value, got Struct (NameType = Variant[String, Array[String]] name, Optional[ValueType] value_type, Optional[MergeType] merge, DefaultValueType = Any default_value) rejected: expects 4 arguments, got 1 (NameType = Variant[String, Array[String]] name, ValueType = Type value_type?, MergeType = Variant[String[1], Hash[String, Scalar]] merge?) rejected: parameter 'name' expects a NameType = Variant[String, Array[String]] value, got Struct (OptionsWithName = Struct[{'name' => NameType = Variant[String, Array[String]], 'value_type' => Optional[ValueType = Type], 'default_value' => DefaultValueType = Any, 'override' => Optional[Hash[String, Any]], 'default_values_hash' => Optional[Hash[String,
Jira (PUP-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Fabien Wernli commented on PUP-6759 Re: systemd provider does not understand "indirect" status / tries to turn off service on each run We have the same problem with rpcbind: is-enabled returns 'indirect', and puppet thinks it's not enabled. But we actually need it enabled+running, so in our case, `indirect` should probably return true? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1743) Environment variable override for structured facts
Title: Message Title
Fabien Wernli commented on FACT-1743
Re: Environment variable override for structured facts
I find the FACTER_foo method very useful for debugging purposes. I think it would be great to be able to override structured facts too.
IMHO it would suffice to be able to override the whole contents of the fact, not just a subset, e.g.
# FACTER_os=''{"name"=>"Debian", "family"=>"Debian", "release"=>{"major"=>"9", "minor"=>"3", "full"=>"9.3"}, "lsb"=>{"distcodename"=>"stretch", "distid"=>"Debian", "distdescription"=>"Debian GNU/Linux 9.3 (stretch)", "distrelease"=>"9.3", "majdistrelease"=>"9", "minordistrelease"=>"3"}}' puppet agent --test
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6640) The function generate() should merge stdout and stdin
Title: Message Title Fabien Wernli commented on PUP-6640 Re: The function generate() should merge stdout and stdin See https://tickets.puppetlabs.com/browse/PUP-6617 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Fabien Wernli commented on PUP-6617 Re: puppet4 function generate() should throw exception when command fails https://tickets.puppetlabs.com/browse/PUP-6640 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6640) The function generate() should merge stdout and stdin
Title: Message Title Fabien Wernli created an issue Puppet / PUP-6640 The function generate() should merge stdout and stdin Issue Type: Bug Affects Versions: PUP 4.5.3 Assignee: Unassigned Created: 2016/08/19 7:25 AM Environment: master Platform: CentOS 7.2.1511 Architecture: x86_64 Linux ccsvli80 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux puppetserver --version puppetserver version: 2.4.0 puppetserver gem list Warning: The following options to parse-opts are unrecognized: :flag LOCAL GEMS *** collectd-dsl (0.3.6cc, 0.3.5) hiera-eyaml (2.1.0) hiera-eyaml-gpg (0.6) highline (1.6.21) jar-dependencies (0.1.13) jruby-openssl (0.9.7 java) json (1.8.0 java) mini_portile2 (2.1.0) rake (10.1.0) rdoc (4.1.2) ruby_gpg (0.3.2) trollop (2.1.2) uuidtools (2.1.5) agent Platform: CentOS 7.2.1511 Architecture: x86_64 Linux ccosvms0033 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 23 17:05:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux rpm -q puppet puppet-3.7.2-1.el7.noarch Priority: Normal Reporter: Fabien Wernli description The function generate() does not merge stdout and stderr using a puppet4 master. It works as expected on a v3
Jira (PUP-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Fabien Wernli commented on PUP-6617 Re: puppet4 function generate() should throw exception when command fails yes, I meant it works using puppet apply. The only environment this seems to be failing in is in agent mode against a v4 server. Also, STDIN/STDOUT handling seems broken (combine option in Util Execute) Cheers Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Fabien Wernli commented on PUP-6617 Re: puppet4 function generate() should throw exception when command fails I can confirm this works as expected using puppet agent 4.5.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Fabien Wernli created an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Issue Type: Bug Affects Versions: PUP 4.5.3 Assignee: Unassigned Created: 2016/08/16 1:55 AM Environment: master Platform: CentOS 7.2.1511 Architecture: x86_64 Linux ccsvli80 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux puppetserver --version puppetserver version: 2.4.0 puppetserver gem list Warning: The following options to parse-opts are unrecognized: :flag LOCAL GEMS *** collectd-dsl (0.3.6cc, 0.3.5) hiera-eyaml (2.1.0) hiera-eyaml-gpg (0.6) highline (1.6.21) jar-dependencies (0.1.13) jruby-openssl (0.9.7 java) json (1.8.0 java) mini_portile2 (2.1.0) rake (10.1.0) rdoc (4.1.2) ruby_gpg (0.3.2) trollop (2.1.2) uuidtools (2.1.5) agent Platform: CentOS 7.2.1511 Architecture: x86_64 Linux ccosvms0033 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 23 17:05:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Jira (HI-531) hiera_array() creates literal ENC[...] array element along with decrypted string
Title: Message Title Fabien Wernli commented on HI-531 Re: hiera_array() creates literal ENC[...] array element along with decrypted string As suggested by R.I. Pienaar on IRC, this seems to be a hiera-eyaml issue instead. Here's the associated issue https://github.com/TomPoulton/hiera-eyaml/issues/205 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-531) hiera_array() creates literal ENC[...] array element along with decrypted string
Title: Message Title Fabien Wernli created an issue Hiera / HI-531 hiera_array() creates literal ENC[...] array element along with decrypted string Issue Type: Bug Affects Versions: HI 3.2.0 Assignee: Unassigned Created: 2016/08/10 2:04 AM Environment: Platform: Linux CentOS 7.2.1511 Architecture: x86_64 RPM: puppetserver-2.4.0-1.el7.noarch $ puppetserver gem list Warning: The following options to parse-opts are unrecognized: :flag LOCAL GEMS *** collectd-dsl (0.3.5) hiera-eyaml (2.1.0) hiera-eyaml-gpg (0.6) highline (1.6.21) jar-dependencies (0.1.13) jruby-openssl (0.9.7 java) json (1.8.0 java) rake (10.1.0) rdoc (4.1.2) ruby_gpg (0.3.2) trollop (2.1.2) uuidtools (2.1.5) Priority: Major Reporter: Fabien Wernli
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title Fabien Wernli commented on FACT-1356 Re: External facts should be able to return structured data For consistency this should also allow using YAML. One easy solution would be to check extension and executable bit Examples: 1. executable foo.yaml → ./foo.yaml | parse_yaml 2. not executable bar.json → parse_json bar.json 3. executable bar → ./bar | parse_key_value etc. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4799) Documentation lacks puppet requirement in metadata.json
Title: Message Title Fabien Wernli created an issue Puppet / PUP-4799 Documentation lacks puppet requirement in metadata.json Issue Type: Improvement Affects Versions: PUP 3.7.5 Assignee: Unassigned Components: Modules Created: 2015/06/30 7:46 AM Priority: Normal Reporter: Fabien Wernli The module development documentation does not mention how to constrain puppet version requirements using the requirement key in metadata.json Add Comment
Jira (PUP-4680) puppetlabs/concat validate_cmd is a noop
Title: Message Title Fabien Wernli created an issue Puppet / PUP-4680 puppetlabs/concat validate_cmd is a noop Issue Type: Bug Affects Versions: PUP 3.7.5 Assignee: Unassigned Components: Modules Created: 2015/06/02 7:37 AM Priority: Major Reporter: Fabien Wernli Looking at the code, the concat_file::validate_cmd was apparently forgotten in release v2.0.0. It used to work in 1.2 Add Comment
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title Fabien Wernli commented on PUP-4421 Re: Virtual resource collectors incorrectly collect exported resources from same node No regression, just something I came across while writing a module. The documentation is confusing ( https://docs.puppetlabs.com/puppet/latest/reference/lang_collectors.html) It explicitly states exported collectors do not collect virtual resources (https://docs.puppetlabs.com/puppet/latest/reference/lang_exported.html#exported-resource-collectors). However, I didn't find an explicit mention for the opposite, i.e. what about virtual resource collectors. So either this is a bug, or a docbug/doc_improvement. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title Fabien Wernli commented on PUP-4421 Re: Virtual resource collectors incorrectly collect exported resources from same node How do I repurpose this to a doc-ticket ? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title
Fabien Wernli created an issue
Puppet / PUP-4421
Virtual resource collectors incorrectly collect exported resources from same node
Issue Type:
Bug
Affects Versions:
PUP 3.7.5
Assignee:
Unassigned
Created:
2015/04/16 12:57 AM
Environment:
linux EL6 and debian8
Priority:
Major
Reporter:
Fabien Wernli
Virtual resource collectors incorrectly collect exported resources from same node. This can very easily be reproduced using:
puppet apply -e '@@notify {should not be collected:}
Notify | |'
This behaviour also appears in agent/master mode
Add Comment
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title Fabien Wernli commented on PUP-4421 Re: Virtual resource collectors incorrectly collect exported resources from same node Negative Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-299) structured facts not available in hiera
Title: Message Title
Fabien Wernli created an issue
Hiera / HI-299
structured facts not available in hiera
Issue Type:
Bug
Affects Versions:
HI 1.3.4
Assignee:
Unassigned
Created:
2014/11/21 5:36 AM
Environment:
Linux 2.6.32-431.11.2.el6.x86_64
Priority:
Normal
Reporter:
Fabien Wernli
It does not seem possible to use structured facts in hiera. I tried many different syntaxes of extracting values e.g. os['name'] but even putting % {os}
in a yaml file in hiera expands to an empty string
Add Comment
