Jira (BOLT-340) Parameters passed as environment variables with ssh are not properly escaped
Title: Message Title Alex Dreyer moved an issue Puppet Task Runner / BOLT-340 Parameters passed as environment variables with ssh are not properly escaped Change By: Alex Dreyer Key: PE BOLT - 23623 340 Project: Puppet Enterprise [Internal] Task Runner 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 (PUP-8463) Remove existing warnings and run PRs through 'ruby -wc'
Title: Message Title Josh Cooper commented on PUP-8463 Re: Remove existing warnings and run PRs through 'ruby -wc' And https://github.com/puppetlabs/puppet/commit/8752d863f4850808a2010939b77a7c39e8f6ee63 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 (PUP-8464) puppet help should process its arguments better
Title: Message Title Jacob Helwig commented on PUP-8464 Re: puppet help should process its arguments better Merged to master in ddfe71b39b. 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 (PUP-8467) Starting to get broken pipe (HTTP 500) on certain manifest - gone after restarting puppetserver
Title: Message Title Josh Cooper commented on PUP-8467 Re: Starting to get broken pipe (HTTP 500) on certain manifest - gone after restarting puppetserver Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/a38025253045ff4e06fd68a536baba035b7a4435 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 (PUP-8467) Starting to get broken pipe (HTTP 500) on certain manifest - gone after restarting puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8467 Starting to get broken pipe (HTTP 500) on certain manifest - gone after restarting puppetserver Change By: Josh Cooper Fix Version/s: PUP 4.10.11 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 (BOLT-339) Inventory file docs are not clear and inconsistent
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-339
Inventory file docs are not clear and inconsistent
Change By:
Michael Smith
'Hosts' and 'Nodes' are used inconsistently. Everywhere it says 'Hosts' should say 'Nodes', same with code that uses {{hosts:}} should use {{nodes:}} instead. The example after "Override a user for a specific node." should also use {{name:}} instead of {{host:}}. Also {{transport:}} should be {{transports:}}. [ https://puppet.com/docs/bolt/0.x/inventory_file.html#objects ] where it talks about the Host is slightly unclear about there being examples of 3 different formats shown. I'd like to update rename the Host entry to Node and update it to {quote} ... For example, a node block could contain any of the following{code} - "host1.example.com"- name: "host1.example.com"- name: "host1.example.com" config:transport: "ssh"{code} {quote} The Group entry should be updated to say "{{nodes : Nodes}} object ..."
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-339) Inventory file docs are not clear and inconsistent
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-339
Inventory file docs are not clear and inconsistent
Change By:
Michael Smith
'Hosts' and 'Nodes' are used inconsistently. Everywhere it says 'Hosts' should say 'Nodes', same with code that uses {{hosts:}} should use {{nodes:}} instead.The example after "Override a user for a specific node." should also use {{name:}} instead of {{host:}}. Also {{transport:}} should be {{transports:}}.https://puppet.com/docs/bolt/0.x/inventory_file.html#objects where it talks about the Host is slightly unclear about there being examples of 3 different formats shown. I'd like to update the Host entry to {quote} ... For example, a node block could contain any of the following{code}- "host1.example.com"- name: "host1.example.com"- name: "host1.example.com" config:transport: "ssh"{code} {quote} The Group entry should be updated to say "{{nodes : Nodes}} object ..."
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-7842) language for SLES 11.3 service not being set correctly during boot
Title: Message Title Branan Riley updated an issue Puppet / PUP-7842 language for SLES 11.3 service not being set correctly during boot Change By: Branan Riley Labels: SLES i18n packaging 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 (PUP-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Jacob Helwig commented on PUP-8443 Re: Topscope 'environment' can become nil when setting node parameters in a custom terminus The PR was merged to the 5.3.x branch in 0feb51b9a7. 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 (BOLT-198) Add 'bolt task show' instructions to error message for incorrect task
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-198 Add 'bolt task show' instructions to error message for incorrect task Change By: Alex Dreyer Release Notes Summary: Better error message when a task or plan is not found Release Notes: Bug Fix 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 (BOLT-198) Add 'bolt task show' instructions to error message for incorrect task
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet Task Runner / BOLT-198 Add 'bolt task show' instructions to error message for incorrect task Change By: Alex Dreyer Assignee: Alex Dreyer 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 (PUP-8467) Starting to get broken pipe (HTTP 500) on certain manifest - gone after restarting puppetserver
Title: Message Title Justin Stoller moved an issue Puppet / PUP-8467 Starting to get broken pipe (HTTP 500) on certain manifest - gone after restarting puppetserver Change By: Justin Stoller Key: SERVER PUP - 2059 8467 Project: Puppet Server 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 (BOLT-339) Inventory file docs are not clear and inconsistent
Title: Message Title Alex Dreyer commented on BOLT-339 Re: Inventory file docs are not clear and inconsistent I think 'node' since the array is 'nodes' as well. 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 (PUP-8428) Manually smoke test all artifacts (Puppet Platform 5.4.0)
Title: Message Title Casey Williams commented on PUP-8428 Re: Manually smoke test all artifacts (Puppet Platform 5.4.0) I've made a winston pr here that adds a new ticket (separate from this one) for the agent lead to run repo smoke tests: https://github.com/puppetlabs/winston/pull/124 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 (PUP-8466) Update winston to clarify pre- and post- release validation smoke testing
Title: Message Title Casey Williams commented on PUP-8466 Re: Update winston to clarify pre- and post- release validation smoke testing PR here: https://github.com/puppetlabs/winston/pull/124 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 (BOLT-339) Inventory file docs are not clear and inconsistent
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-339
Inventory file docs are not clear and inconsistent
Change By:
Michael Smith
'Hosts' and 'Nodes' are used inconsistently. Everywhere it says 'Hosts' should say 'Nodes', same with code that uses {{hosts:}} should use {{nodes:}} instead. The example after "Override a user for a specific node." should also use {{name:}} instead of {{host:}}. Also {{transport:}} should be {{transports:}}. https://puppet.com/docs/bolt/0.x/inventory_file.html#objects where it talks about the Host is slightly unclear about there being examples of 3 different formats shown. I'd like to update the Host entry to... For example, a node block could contain any of the following{code}- "host1.example.com"- name: "host1.example.com"- name: "host1.example.com" config:transport: "ssh"{code} The Group entry should be updated to say "{{nodes : Nodes}} object ..."
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
Jira (BOLT-339) Inventory file docs are not clear and inconsistent
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-339 Inventory file docs are not clear and inconsistent Change By: Michael Smith Assignee: Kate Lopresti 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 (BOLT-339) Inventory file docs are not clear and inconsistent
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-339 Inventory file docs are not clear and inconsistent Change By: Michael Smith Priority: Normal Major 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 (BOLT-339) Inventory file docs are not clear and inconsistent
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-339 Inventory file docs are not clear and inconsistent Change By: Michael Smith Sprint: Bolt Kanban 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 (BOLT-339) Inventory file docs are not clear and inconsistent
Title: Message Title Michael Smith commented on BOLT-339 Re: Inventory file docs are not clear and inconsistent Alex Dreyer should we refer to Host or Node for a single entry throughout that doc? It looks like at the top we talk about a node, so maybe we should use that instead of host. 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 (BOLT-339) Inventory file docs are not clear and inconsistent
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-339 Inventory file docs are not clear and inconsistent Issue Type: Bug Assignee: Unassigned Created: 2018/02/15 11:09 AM Priority: Normal Reporter: Michael Smith 'Hosts' and 'Nodes' are used inconsistently. Everywhere it says 'Hosts' should say 'Nodes', same with code that uses hosts: should use nodes: instead. The example after "Override a user for a specific node." should also use name: instead of host:. Also transport: should be transports:. https://puppet.com/docs/bolt/0.x/inventory_file.html#objects where it talks about the Host is slightly unclear about there being examples of 3 different formats shown. I'd like to update the Host entry to ... For example, a node block could contain any of the following - "host1.example.com" - name: "host1.example.com" - name: "host1.example.com" config: transport: "ssh"
Jira (BOLT-318) I want to refer to inventory groups as targets
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-318 I want to refer to inventory groups as targets Change By: Michael Smith Release Notes Summary: The name of a group from inventory can be passed in place of a node name to --nodes or as a target to the fun run functions. Bolt's run functions will now parse comma and space separated lists of names into node URIs and/or groups, so explicit parsing in a plan is no longer necessary. This makes sense to add to the section at https://puppet.com/docs/bolt/0.x/bolt_options.html#specifying-nodesA new Bolt function, get_targets, is added to resolve a comma-separated string or array of node URIs and/or groups into an array of Target objects. 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 (BOLT-330) Users should be able to use wildcards to target nodes in inventory
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-330 Users should be able to use wildcards to target nodes in inventory Change By: Michael Smith Release Notes Summary: You can refer to nodes enumerated in inventory using the '*' wild card. For example `puppet task run minifact --nodes ' foo*.example.com ' ` . Note that in most shells, the wildcard will need to be quoted or escaped to avoid shell expansion.This makes sense to add to the section at https://puppet.com/docs/bolt/0.x/bolt_options.html#specifying-nodes 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 (PDB-3848) Release PuppetDB 5.1.z(Platform 5.3.6 - 2018-04-09)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-3848 Release PuppetDB 5.1.z(Platform 5.3.6 - 2018-04-09) Change By: Nirupama Mantha Summary: Release PuppetDB 5.1.z( Platform 5.3.6 - 2018-04-09) 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 (PDB-3850) Release PuppetDB 5.2(PE 2018.1.0 - 2018-04-17)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-3850 Release PuppetDB 5.2(PE 2018.1.0 - 2018-04-17) Change By: Nirupama Mantha Summary: Release PuppetDB 5.2( PE 2018 .1.0 - 2018- 04-17) 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 (PDB-3853) Release PuppetDB 5.2.z(Platform 5.5.0 - 2018-03-14)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-3853 Release PuppetDB 5.2.z(Platform 5.5.0 - 2018-03-14) Change By: Nirupama Mantha Summary: Release PuppetDB 5.2.z( Platform 5.5.0 - 2018-03-14) 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 (PDB-3850) Release PuppetDB 5.2.z(PE 2018.1.0 - 2018-04-17)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-3850 Release PuppetDB 5.2.z(PE 2018.1.0 - 2018-04-17) Change By: Nirupama Mantha Summary: Release PuppetDB 5.2 .z (PE 2018.1.0 - 2018-04-17) 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 (PDB-3849) Release PuppetDB 5.1.z (PE 2016.4.11 - 2018-04-18)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-3849 Release PuppetDB 5.1.z (PE 2016.4.11 - 2018-04-18) Change By: Nirupama Mantha Summary: Release PuppetDB 5.1.z ( PE 2016.4.11 - 2018-04-18) 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 (PDB-3853) Release PuppetDB 5.2.z(2018-03-14)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-3853 Release PuppetDB 5.2.z(2018-03-14) Issue Type: Task Assignee: Unassigned Created: 2018/02/15 10:43 AM Priority: Normal Reporter: Nirupama Mantha Release PuppetDB in preparation for the Puppet Platform 5.5.0 release https://confluence.puppetlabs.com/display/PM/Puppet+Platform+5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8442) type parameters do not honor when default is set to false
Title: Message Title Josh Cooper commented on PUP-8442 Re: type parameters do not honor when default is set to false There's a related issue when setting the desired value of a property to a falsey value in PUP-2368. 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 (PUP-8442) type parameters do not honor when default is set to false
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8442
type parameters do not honor when default is set to false
Change By:
Josh Cooper
Acceptance Criteria:
* parameter defaults of {{false}} are honored and properly set * false values are correctly stored in the last run report and corrective change transactionstore.yaml
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 (PUP-920) Add catalog application information to report
Title: Message Title Melissa Stone updated an issue Puppet / PUP-920 Add catalog application information to report Change By: Melissa Stone Sprint: Platform Core Hopper KANBAN 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 (PUP-920) Add catalog application information to report
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-920 Add catalog application information to report Change By: Melissa Stone Assignee: Melissa Stone 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 (PUP-8428) Manually smoke test all artifacts (Puppet Platform 5.4.0)
Title: Message Title Molly Waggett commented on PUP-8428 Re: Manually smoke test all artifacts (Puppet Platform 5.4.0) yeah, what I've been doing for that is (for one rpm and one deb): wget release package rpm/dpkg install yum/apt update yum/apt install puppet-agent, puppetserver, puppetdb check that the versions are what we just shipped If that ticket was meant for something else, please let me know. 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 (PUP-8466) Update winston to clarify pre- and post- release validation smoke testing
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8466 Update winston to clarify pre- and post- release validation smoke testing Change By: Geoff Nichols Sprint: Platform OS Kanban 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 (PUP-8466) Update winston to clarify pre- and post- release validation smoke testing
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8466 Update winston to clarify pre- and post- release validation smoke testing Change By: Geoff Nichols Team: Platform OS 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 (PUP-8466) Update winston to clarify pre- and post- release validation smoke testing
Title: Message Title Geoff Nichols created an issue Puppet / PUP-8466 Update winston to clarify pre- and post- release validation smoke testing Issue Type: Task Assignee: Casey Williams Created: 2018/02/15 9:41 AM Priority: Normal Reporter: Geoff Nichols Update winston release ticket set to clarify platform pre- and post- release validation steps per comments in PUP-8428. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDOC-215) Type aliases are not handled well
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-215 Type aliases are not handled well Issue Type: New Feature Assignee: Unassigned Created: 2018/02/15 9:37 AM Priority: Normal Reporter: Lee Lowder There is currently no way to document type aliases using Strings. They are not really mentioned in any of the documentation, or the proposed style guide for Strings. They are ignored when documentation is rendered. If a class param uses them, it shows the name of the alias, but NOT what it makes up. There should be some way to separately document these, and the param type listing should link to it or provide it as an expandable element or such. Add Comment This message was sent
Jira (PUP-2368) using booleans result in unmanaged property
Title: Message Title Josh Cooper commented on PUP-2368 Re: using booleans result in unmanaged property PUP-8442 should resolve the issue for parameter defaults. This issue is related, but different because properties are managed and we want to be able to set the current value to false. 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 (PDOC-214) Add ability to customize the template
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-214 Add ability to customize the template Issue Type: New Feature Assignee: Unassigned Created: 2018/02/15 9:34 AM Priority: Normal Reporter: Lee Lowder There should be a simple, documented method for customizing the rendered HTML output - adding custom sections or reordering things, applying custom CSS, etc. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-2368) using booleans result in unmanaged property
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2368 using booleans result in unmanaged property Change By: Josh Cooper Sub-team: Coremunity 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 (PDOC-213) Add support for @note tag
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-213 Add support for @note tag Issue Type: New Feature Assignee: Unassigned Created: 2018/02/15 9:33 AM Priority: Normal Reporter: Lee Lowder Strings should support the @note YARD tag in rendered documentation. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-2368) using booleans result in unmanaged property
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2368 using booleans result in unmanaged property Change By: Josh Cooper Sprint: Platform Core Grooming 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 (PDOC-212) Add support for @todo tag
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-212 Add support for @todo tag Issue Type: New Feature Assignee: Unassigned Created: 2018/02/15 9:32 AM Priority: Normal Reporter: Lee Lowder Strings should support the YARD @todo tag in rendered documentation. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDOC-211) Add support for generating a "meta index"
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-211 Add support for generating a "meta index" Issue Type: New Feature Assignee: Unassigned Created: 2018/02/15 9:28 AM Priority: Normal Reporter: Lee Lowder when you run `puppet strings server` it parses all the modules in your modulepath and then generates a master/meta index. This is not currently possible to do using `puppet strings generate` which is done per module. It would be super useful to be able to feed generate a list of modules or a modulepath and have it generate documentation like puppet strings server does. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-328) Don't pass task paths to run_task
Title: Message Title David Kramer assigned an issue to Nick Lewis Puppet Task Runner / BOLT-328 Don't pass task paths to run_task Change By: David Kramer Assignee: Nick Lewis 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 (BOLT-316) Orchestrator transport should batch run_* commands
Title: Message Title David Kramer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-316 Orchestrator transport should batch run_* commands Change By: David Kramer Assignee: Nick Lewis Alex Dreyer 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 (BOLT-198) Add 'bolt task show' instructions to error message for incorrect task
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-198 Add 'bolt task show' instructions to error message for incorrect task Change By: Michael Smith Assignee: Michael Smith Alex Dreyer 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 (PUP-8241) Update contributor documents
Title: Message Title Jorie Tappa commented on PUP-8241 Re: Update contributor documents It looks like Melissa may have taken care of the CONTRIBUTING.md portion of this already. 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 (PDB-3830) Command Queue Grows Steadily Over Time not related to load
Title: Message Title Jeff Yarnell commented on PDB-3830 Re: Command Queue Grows Steadily Over Time not related to load Russell Mull Please see Nick's question above. 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 (PUP-8444) Have "puppet man" default to "--help" when run without arguments
Title: Message Title Jacob Helwig commented on PUP-8444 Re: Have "puppet man" default to "--help" when run without arguments Merged to master branch in 7ece5dea6a. 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 (PDB-3830) Command Queue Grows Steadily Over Time not related to load
Title: Message Title Nick Walker commented on PDB-3830 Re: Command Queue Grows Steadily Over Time not related to load Jeff Yarnell yessir, I put my notes in the PR. The only question I had left was whether I should aim the patch at master or stable. 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 (PUP-6595) puppet silently ignores modules with semi-broken metadata.json
Title: Message Title Anthony Leto commented on PUP-6595 Re: puppet silently ignores modules with semi-broken metadata.json During engagement, Customer noticed this error as well. Customer asked me to troubleshoot, we ended up finding this error due to source not being specified in the metadata.json. 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 (PUP-8428) Manually smoke test all artifacts (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey commented on PUP-8428 Re: Manually smoke test all artifacts (Puppet Platform 5.4.0) Geoff Nichols RE-10233 is the ticket for it, but its description may need to be updated to better capture the intent of the test procedure (per John's notes). 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 (PUP-8428) Manually smoke test all artifacts (Puppet Platform 5.4.0)
Title: Message Title Geoff Nichols commented on PUP-8428 Re: Manually smoke test all artifacts (Puppet Platform 5.4.0) Thanks Kenn Hussey, do you know if that follow-up task is tracked anywhere? If not, I'd love to create a ticket for it. One note - just in case this context is not widely shared - here's John Duarte's explanation to me of his intent for these two test procedures. : The packages script is intended to be executed prior to a release in order to validate that all of the prospective release packages play nicely together. For the most part, this validation is automated via the PuppetDB acceptance smoke CI job. However, I like to use it as a method of ensuring that PDB can be manually installed as per our documentation and still work with the rest of the platform suite. The repo script cannot be executed until after the release because we do not have a staging environment for the repodata currently. It is a heavier set of validation intended to ensure that PDB can be installed via the existing module and the manual process with the expected results. 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
Jira (PUP-8431) Communicate scope and timeline of next release (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8431 Communicate scope and timeline of next release (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13)1. Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group.2. Create or update the Kanban board for the release series . Ensure that the underlying filter for the board include includes issues from the release filter and add a quick filter to highlight just those issues.3. Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”.4. Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed.5. Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages.6. Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page.7. Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release. Add Comment
Jira (PUP-8430) Update Confluence and JIRA based on release (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8430 Update Confluence and JIRA based on release (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13)1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”.2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”.3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates.4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date.5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers.6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers.7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description and release date of each version as needed based on what was shipped when. 8) Update the Kanban board for the release series. Remove the release filter from the underlying filter for the board and remove the quick filter for the release as well. Add Comment
Jira (PUP-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8231 Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp) Change By: Kenn Hussey Flagged: Impediment 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 (PUP-8423) FIPS-Enabled Puppet Server Side
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8423 FIPS-Enabled Puppet Server Side Change By: Kenn Hussey Fix Version/s: PUP 5.y Fix Version/s: PUP 5.5.0 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 (PUP-8430) Update Confluence and JIRA based on release (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8430 Update Confluence and JIRA based on release (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13)1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages under to the appropriate parent pages under “Current Releases”.2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”.3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates.4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date.5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers.6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers.7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description and release date of each version as needed based on what was shipped when. Add Comment
Jira (PDB-3852) PuppetDB query nodes based on fact broken
Title: Message Title
Mateusz Gozdek created an issue
PuppetDB / PDB-3852
PuppetDB query nodes based on fact broken
Issue Type:
Bug
Affects Versions:
PDB 5.2.0
Assignee:
Unassigned
Components:
PuppetDB
Created:
2018/02/15 5:53 AM
Environment:
OS: Ubuntu 16.04 PuppetDB version: 5.2.0
Priority:
Normal
Reporter:
Mateusz Gozdek
It seems that after updating PuppetDB from 5.1.4 to 5.2, some queries stopped working for us, for example this one:
inventory[certname] { facts.mcollective.server.collectives.match("\d+") = "mcollective" }
Against following facts structure:
"mcollective": {
Jira (BOLT-332) Target objects should store state of the Targets
Title: Message Title
Thomas Hallgren commented on BOLT-332
Re: Target objects should store state of the Targets
Please consider using an immutable construct for this. What we could do is to implement something that would allow building of lists that doesn't expose the list until it's complete. Let's assume that we create a build_array method that calls its lambda until it breaks out. Each call gets the current size of the built array and the last element added as arguments $size, $prev:
$results = build_array($max_iterations) |$size, $prev| {
if $prev < 5 {
break
}
run_task('check', $node).first['val']
}
similar design to build a hash. $pv and $pk is the previously added entry. Each iteration returns a two elemen array (key, value):
$results = build_hash($max_iterations) |$size, $pk, $pv| {
if $pv < 5 {
break
}
Jira (PUP-7068) Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-7068 Re: Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml Returned this ticket to "closed/fixed" state as the problem described here was fixed and released in Puppet 4.9.0. 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 (BOLT-332) Target objects should store state of the Targets
Title: Message Title Henrik Lindberg commented on BOLT-332 Re: Target objects should store state of the Targets We don't have a `while` statement. It is acceptable that there are objects with mutable state where you get immutable / snapshot values by calling its methods. That is similar to calling functions that return different values for different inputs - and we have no constraint that forbids that - i.e. functions in puppet are not mathematically pure. As an example, you must not return say a hash of values, that later gets modified. We don't want users to have to know such things and we would need functions to copy/dup structures to allow users to protect their logic from such problems. So, yes, immutability of values is much preferred. That is not the same as immutability of variables. While it cannot be allowed in general in the puppet language (because of lazy code evaluation and use of fully qualified variables), it could possibly be allowed for local variables. 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 (PUP-8441) Error datatype should support to_json
Title: Message Title Henrik Lindberg commented on PUP-8441 Re: Error datatype should support to_json Suggest we add an API to PAL for serialization to make it super simple to use while still doing the right thing. Regarding your question how to make an object appear as an array - not sure I understand, are you thinking about a conversion - a result of a different data type? I can imagine adding a mechanism to the API I am suggesting that gets called when particular data types are to be serialized and allowing override of default behavior. I think the Error data type is of general value in Puppet. 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 (PUP-7068) Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-7068 Re: Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml Hm, this ticket is still "Open", but it says it was merged to master. What is the correct state of this ticket? 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.
