Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Dimitri Tischenko updated an issue Puppet / PUP-10113 Functions are slower if called with chained syntax than with prefix syntax Change By: Dimitri Tischenko Environment: [^test.log] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332233.1572273925000.11233.1572374760198%40Atlassian.JIRA.
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Dimitri Tischenko updated an issue Puppet / PUP-10113 Functions are slower if called with chained syntax than with prefix syntax Change By: Dimitri Tischenko Environment: [^test. pp][^test. log] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332233.1572273925000.11228.1572374700279%40Atlassian.JIRA.
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title
Dimitri Tischenko updated an issue
Puppet / PUP-10113
Functions are slower if called with chained syntax than with prefix syntax
Change By:
Dimitri Tischenko
*Puppet Version: 5.5.17* *Puppet Server Version: 2018.1* *OS Name/Version: Centos 7* *Desired Behavior:*As documented in [https://puppet.com/docs/puppet/5.5/lang_functions.html#chained-function-calls], chained function call syntax should result in same behaviour as prefixed syntax.*Actual Behavior:*Using chained syntax results in slower performance of the function call. The performance depends on the size of the object "before the dot".{{Examples:}} {{ Run puppet apply test.pp --debug --profile}}Please see attached: * test.pp * test.log
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title
Dimitri Tischenko updated an issue
Puppet / PUP-10113
Functions are slower if called with chained syntax than with prefix syntax
Change By:
Dimitri Tischenko
*Puppet Version: 5.5.17* *Puppet Server Version: 2018.1* *OS Name/Version: Centos 7* *Desired Behavior:*As documented in [ here|[ https://puppet.com/docs/puppet/5.5/lang_functions.html#chained-function-calls] ] , chained function call syntax should result in same behaviour as prefixed syntax.*Actual Behavior:*Using chained syntax results in slower performance of the function call. The performance depends on the size of the object "before the dot". {{ Examples: }} {{ Run ` puppet apply test.pp --debug --profile ` }} Please see attached: * test.pp * test.log
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Dimitri Tischenko commented on PUP-10113 Re: Functions are slower if called with chained syntax than with prefix syntax Henrik Lindberg is aware of this and already has a fix. Also pinging Thomas Hallgren for visibility. 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.332233.1572273925000.8757.1572274020183%40Atlassian.JIRA.
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Dimitri Tischenko created an issue Puppet / PUP-10113 Functions are slower if called with chained syntax than with prefix syntax Issue Type: Bug Affects Versions: PUP 5.5.16 Assignee: Unassigned Attachments: test.log, test.pp Created: 2019/10/28 7:45 AM Environment: test.pp test.log Priority: Normal Reporter: Dimitri Tischenko Puppet Version: 5.5.17 Puppet Server Version: 2018.1 OS Name/Version: Centos 7 Desired Behavior: As documented [here|https://puppet.com/docs/puppet/5.5/lang_functions.html#chained-function-calls], chained function call syntax should result in same behaviour as prefixed syntax. Actual Behavior: Using chained syntax results in slower performance of the function call. The performance depends on the size of the object "before the dot". Examples: Run `puppet apply test.pp --debug --profile` Please see attached: test.pp test.log
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Dimitri Tischenko commented on BOLT-1466 Re: Inventory configuration precedence is confusing Just tested a work-around by placing the pcp group at the top of the inventory file. This effectively forces bolt to use the pcp transport for the nodes from puppetdb, but it creates an inverse problem: now, the transport for nodes defined further down in the inventoryfile is ignored - all nodes which are also member of the pcp group now connect over pcp. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315922.1562780625000.12070.1562836440086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title
Dimitri Tischenko commented on BOLT-1466
Re: Inventory configuration precedence is confusing
The confusion arises especially with dynamically populated groups. For instance, if using this group:
targets:
- _plugin: puppetdb
query: "nodes[] { }"
config:
transport: pcp
one would assume that all targets dynamically acquired by the puppetdb plugin will be guaranteed to connect over pcp. However, due to the way inventory parsing is implemented, if that node name is defined elsewhere in the inventory file with a different transport, bolt will prefer that definition which is not what the user expects.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title Dimitri Tischenko commented on PUP-9642 Re: puppet device permissions preventing reading dirs David Schmitt As per the docs at https://puppet.com/docs/pe/2018.1/component_versions_in_recent_pe_releases.html, the current LTS release of PE uses agent 5.5.10, so customers currently using this version (including Deutsche Telekom) have this issue. Do we have a work-around for them short of upgrading to PE 2019.0? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-394) SPIKE: Propose changes to puppet task spec to include multiple task implementations
Title: Message Title Dimitri Tischenko commented on BOLT-394 Re: SPIKE: Propose changes to puppet task spec to include multiple task implementations Does this include enabling multiple files per task? See OPTY-127 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1079) Exported resources is exporting to the database with --noop flag
Title: Message Title Dimitri Tischenko commented on PUP-1079 Re: Exported resources is exporting to the database with --noop flag (Comment triggered by DOCUMENT-832) FWIW, I have a customer who is happy with the --noop mode preventing exported resources from expiration. From their perspective, if the agent does something useful on the node and a report gets sent, it's OK for exported resources to be updated. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6553) Environment compiler and app_management language need to support hiera lookups
Title: Message Title
Dimitri Tischenko commented on PUP-6553
Re: Environment compiler and app_management language need to support hiera lookups
Thanks to Reid Vandewiele we can confirm there is, in fact, a work-around for this issue using Hiera 5. The only thing which is needed is to allow the value to be looked up from a hierarchy not using any node-level variables. Example:
---
# managed by puppet
version: 5
defaults:
datadir: /etc/puppetlabs/code/environments/%{environment}/hieradata
data_hash: yaml_data
hierarchy:
