Jira (BOLT-464) Publish Bolt to chocolatey.org
Title: Message Title Glenn Sarti commented on BOLT-464 Re: Publish Bolt to chocolatey.org Merged into master at; https://github.com/puppetlabs/puppet-chocolatey-packages/commit/39f76edf078e423a698672230d375a03064185ee The next update cycle (4am UTC) will push the puppet-bolt package 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-8890) 5.5 docs missing schema files
Title: Message Title Josh Cooper assigned an issue to Garrett Guillotte Puppet / PUP-8890 5.5 docs missing schema files Change By: Josh Cooper Assignee: Garrett Guillotte 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-8890) 5.5 docs missing schema files
Title: Message Title Josh Cooper commented on PUP-8890 Re: 5.5 docs missing schema files Thanks for letting us know Alex Monk. 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-6828) Simplify agent SSL initialization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6828 Simplify agent SSL initialization Change By: Maggie Dreyer Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6828) Simplify agent SSL initialization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6828 Simplify agent SSL initialization Change By: Maggie Dreyer Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6828) Simplify agent SSL initialization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6828 Simplify agent SSL initialization Change By: Maggie Dreyer Team/s: Platform Core Server 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-8890) 5.5 docs missing schema files
Title: Message Title Alex Monk created an issue Puppet / PUP-8890 5.5 docs missing schema files Issue Type: Bug Affects Versions: PUP 5.5.1, PUP 5.5.0 Assignee: Unassigned Components: DOCS Created: 2018/05/24 4:51 PM Priority: Trivial Reporter: Alex Monk e.g. https://puppet.com/docs/puppet/5.4/schemas/file_metadata.json vs. https://puppet.com/docs/puppet/5.5/schemas/file_metadata.json which is a 404 for some reason other schema files I checked are also missing, but this one in particular is linked from https://puppet.com/docs/puppet/5.5/http_api/http_file_metadata.html#schema Add Comment
Jira (BOLT-519) Bolt should send a Bolt user agent header to orchestrator
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-519 Bolt should send a Bolt user agent header to orchestrator Change By: Michael Smith Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8733) File type redefined when required in code
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8733 File type redefined when required in code Change By: Maggie Dreyer Team: Server 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-8770) Puppet resource service status should be more than binary
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Adam Bottchen CS Priority: Needs Priority Reviewed 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-8799) Release 1.0.0 to the forge
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8799 Release 1.0.0 to the forge Change By: Melissa Stone Assignee: Melissa Stone 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-8577) Extract selinux type/provider into a module
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8577 Extract selinux type/provider into a module Change By: Melissa Stone Sprint: Platform Core Hopper KANBAN 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-8796) Create the github repo
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8796 Create the github repo Change By: Melissa Stone Assignee: Melissa Stone 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-8802) Move all outstanding PUP tickets to Modules
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8802 Move all outstanding PUP tickets to Modules Change By: Melissa Stone Assignee: Melissa Stone 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-8801) Remove type/provider code from puppet
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8801 Remove type/provider code from puppet Change By: Melissa Stone Assignee: Melissa Stone 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-8797) Extract the code & verify the module
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8797 Extract the code & verify the module Change By: Melissa Stone Assignee: Melissa Stone 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-8798) Create the CI pipeline
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8798 Create the CI pipeline Change By: Melissa Stone Assignee: Melissa Stone 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-8577) Extract selinux type/provider into a module
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8577 Extract selinux type/provider into a module Change By: Melissa Stone Assignee: Melissa Stone 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-8800) Package module into puppet-agent
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8800 Package module into puppet-agent Change By: Melissa Stone Assignee: Melissa Stone 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-8889) Puppet Agent : cannot add certificates for HTTPS
Title: Message Title Branan Riley moved an issue Puppet / PUP-8889 Puppet Agent : cannot add certificates for HTTPS Change By: Branan Riley Affects Version/s: puppet-agent 5.5.1 Affects Version/s: puppet-agent 1.10.9 Affects Version/s: PUP 4.10.9 Affects Version/s: PUP 5.5.1 Key: PA PUP - 2059 8889 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-7822) Add get(), getvar() functions that use dot syntax to "dig" into hash/array
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-7822
Add get(), getvar() functions that use dot syntax to "dig" into hash/array
Change By:
Reid Vandewiele
Supporting the dot-notation for digging into structured values (arrays and hashes) is of value. The current available function {{dig()}} does not parse the dot notation (it takes an array of segments) and it cannot be changed as that would break compatibility, and it also does not support a default value.A new function {{get()}} that also takes an optional lambda that gets called if the result would be undef. If the lambda takes no arguments it is simply called. If it accepts one argument, that is a {{Struct\[segments => Array\[String], values => Array]}}, thus making it possible to figure out how far the "dig" got before giving up, and to use that in a custom warning or error message (or simply logging it when debugging). (The value array ends with the undef value that caused the dig to give up). The lambda is not called if the final segment results in a nil value being found in a hash, but is called if the last segment did not exist.A new companion function to {{get()}}, {{getvar(".")}}.Examples:{code:puppet}$facts.get('some.fact')getvar('facts.some.fact')$facts.get('some.fact') || { 'go fish' } # 'go fish' is the defaultgetvar('facts.some.fact') || { 'go fish' }$ fact facts .get('some.facts.detail.0.x') |$resolution| { $size = $resolution['values'].size() # std lib function for now since size is not in core notice(@("MESSAGE"))Could not lookup all given segments: ${resolution['segments']}Got an undef value for the key: ${resolution['segments'][$size-1]}Values per segment are: ${resolution['values']}|- MESSAGE}{code}When implementing this, it is of value to write a helper function {{parse_dig(String)}} that returns an array of segments from the dot-notation string. The {{get}} function uses that if it gets a string, if it gets an array it is taken as already parsed segments. The {{dig}} function should be given the lambda support to process the walked path. Thus:* Add a {{parse_dig(String)}} function* Add a lambda for processing default to {{dig}}* Add {{get(Variant\[Array, String])}}, calling {{parse_dig}} for a String arg, and then calling {{dig}} to do the digging.* Add a default value parameter to {{get}} which is mutually exclusive with giving a lambda - the default value is returned if value is undef (irrespective of reason) - if there is the need to differentiate between actual undef value, and not found, a lambda must be used. ORIGINAL-The fact() function provides a way to use the dot syntax for indexing into structured in the DSL. This was recently merged into stdlib(PR: https://github.com/puppetlabs/puppetlabs-stdlib/pull/787 Docs: https://github.com/puppetlabs/puppetlabs-stdlib#fact). Ideally this would be part of core puppet instead of the stdlib module given it's the syntax used in facter and heira for structured facts.
Jira (PUP-7822) Add get(), getvar() functions that use dot syntax to "dig" into hash/array
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-7822
Add get(), getvar() functions that use dot syntax to "dig" into hash/array
Change By:
Reid Vandewiele
Supporting the dot-notation for digging into structured values (arrays and hashes) is of value. The current available function {{dig()}} does not parse the dot notation (it takes an array of segments) and it cannot be changed as that would break compatibility, and it also does not support a default value.A new function {{get()}} that also takes an optional lambda that gets called if the result would be undef. If the lambda takes no arguments it is simply called. If it accepts one argument, that is a {{Struct\[segments => Array\[String], values => Array]}}, thus making it possible to figure out how far the "dig" got before giving up, and to use that in a custom warning or error message (or simply logging it when debugging). (The value array ends with the undef value that caused the dig to give up). The lambda is not called if the final segment results in a nil value being found in a hash, but is called if the last segment did not exist. A new companion function to {{get()}}, {{getvar(".")}}. Examples:{code:puppet}$facts.get('some.fact') getvar('facts.some.fact') $facts.get('some.fact') || { 'go fish' } # 'go fish' is the default getvar('facts.some.fact') || { 'go fish' } $fact.get('some.facts.detail.0.x') |$resolution| { $size = $resolution['values'].size() # std lib function for now since size is not in core notice(@("MESSAGE"))Could not lookup all given segments: ${resolution['segments']}Got an undef value for the key: ${resolution['segments'][$size-1]}Values per segment are: ${resolution['values']}|- MESSAGE}{code}When implementing this, it is of value to write a helper function {{parse_dig(String)}} that returns an array of segments from the dot-notation string. The {{get}} function uses that if it gets a string, if it gets an array it is taken as already parsed segments. The {{dig}} function should be given the lambda support to process the walked path. Thus:* Add a {{parse_dig(String)}} function* Add a lambda for processing default to {{dig}}* Add {{get(Variant\[Array, String])}}, calling {{parse_dig}} for a String arg, and then calling {{dig}} to do the digging.* Add a default value parameter to {{get}} which is mutually exclusive with giving a lambda - the default value is returned if value is undef (irrespective of reason) - if there is the need to differentiate between actual undef value, and not found, a lambda must be used. ORIGINAL-The fact() function provides a way to use the dot syntax for indexing into structured in the DSL. This was recently merged into stdlib(PR: https://github.com/puppetlabs/puppetlabs-stdlib/pull/787 Docs: https://github.com/puppetlabs/puppetlabs-stdlib#fact). Ideally this would be part of core puppet instead of the stdlib module given it's the syntax used in facter and heira for structured facts.
Jira (PUP-7822) Add get(), getvar() functions that use dot syntax to "dig" into hash/array
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-7822 Add get(), getvar() functions that use dot syntax to "dig" into hash/array Change By: Reid Vandewiele Acceptance Criteria: A get() function that supports the dot-syntax for digging into a value and that optionally handles returning a default value if the result would otherwise be undef. A getvar() function that digs into a value when given a . dot-syntax string, where is a variable name 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-7822) Add get(), getvar() functions that use dot syntax to "dig" into hash/array
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-7822 Add get(), getvar() functions that use dot syntax to "dig" into hash/array Change By: Reid Vandewiele Summary: Add a get() function , getvar() functions that supports use dot syntax to "dig" into hash/array 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-541) Send release announcements (Bolt 0.20.3)
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-541 Send release announcements (Bolt 0.20.3) Change By: Yasmin Rajabi Sub-team: Bolt 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-540) Docs for bolt release (Bolt 0.20.3)
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-540 Docs for bolt release (Bolt 0.20.3) Change By: Yasmin Rajabi Sub-team: Bolt 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-539) Kick off release pipeline (Bolt 0.20.3)
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-539 Kick off release pipeline (Bolt 0.20.3) Change By: Yasmin Rajabi Sub-team: Bolt 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-538) Reconcile git commits, JIRA tickets, and versions (Bolt 0.20.3)
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-538 Reconcile git commits, JIRA tickets, and versions (Bolt 0.20.3) Change By: Yasmin Rajabi Sub-team: Bolt 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-8888) Summer 2018 AIX User/Group Fixes
Title: Message Title Branan Riley moved an issue Puppet / PUP- Summer 2018 AIX User/Group Fixes Change By: Branan Riley Key: CPR PUP - 582 Project: Community Package Repository Puppet 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-464) Publish Bolt to chocolatey.org
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-464 Publish Bolt to chocolatey.org Change By: Lucy Wyman Release Notes Summary: This adds the ability to install puppet-bolt on Windows with the command `choco install puppet-bolt`. The user will need to have chocolatey installed on their system, and we will still have the `.msi` available from http://downloads.puppetlabs.com/windows/. Release Notes: New Feature 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-465) Publish Bolt to Homebrew Cask
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-465 Publish Bolt to Homebrew Cask Change By: Lucy Wyman Assignee: Lucy Wyman 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-8887 Re: puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Not sure if it will work to just revert it, and it makes convert_to more expensive (yet another lookup of lookup_options). 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-686) --detailed-exit-codes not honored when --noop is used
Title: Message Title Rob Nelson commented on PUP-686 Re: --detailed-exit-codes not honored when --noop is used Works for me! 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-686) --detailed-exit-codes not honored when --noop is used
Title: Message Title Jacob Helwig commented on PUP-686 Re: --detailed-exit-codes not honored when --noop is used Depends on what else is in the catalog. The exit code from --detailed-exit-codes is actually a bitmask, so if the resource that was out of sync was noop => true it would set bit 4 (integer 8), if the resource is not noop then it'll set bit 2 (integer 2), so if there were both noop, and non-noop resources that were out of sync, it would have both bits set, and be an exit code of 10. 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-686) --detailed-exit-codes not honored when --noop is used
Title: Message Title Rob Nelson commented on PUP-686 Re: --detailed-exit-codes not honored when --noop is used I think 8 sounds fine for a noop run. When in a yesop run but with noop resources that changed, what would the return code be, 2 or 8? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-542) It should be easy to query PuppetDB with Bolt
Title: Message Title Yasmin Rajabi commented on BOLT-542 Re: It should be easy to query PuppetDB with Bolt Closing as done based on Robb's email. 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-464) Publish Bolt to chocolatey.org
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-464 Publish Bolt to chocolatey.org Change By: Lucy Wyman On release, publish Bolt to chocolatey.org. PDK has some automation at https://github.com/puppetlabs/puppet-chocolatey-packages that we can start from. Publish should be tied into release jobs. The puppet-chocolatey-packages repository has an appveyor job that runs once a day that will look for new packages in http://downloads.puppetlabs.com/windows/ and build a chocolatey package from the MSI there if there's an updated version. This means that once a new package is published (which is already done by Vanagon in our release pipeline), within 24 hours the automatic updater will get run in the chocolatey-packages repo and will publish a new package to chocolatey. 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
Jira (PUP-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8887 puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-8887 Re: puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Henrik Lindberg, the commit that breaks this workflow, can it be reverted? Judging from the comment, it's an optimization. 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8887 puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-686) --detailed-exit-codes not honored when --noop is used
Title: Message Title Jacob Helwig commented on PUP-686 Re: --detailed-exit-codes not honored when --noop is used I'm in favor of Branan Riley's suggestion of using 8 in the exit bitmask to indicate that a noop resource is out of sync, as we can use that even when --noop isn't used, and there are "noop => true" resources in the catalog. 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-542) It should be easy to query PuppetDB with Bolt
Title: Message Title
Paul Anderson updated an issue
Puppet Task Runner / BOLT-542
It should be easy to query PuppetDB with Bolt
Change By:
Paul Anderson
As a system administrator using Open Source Puppet, or Puppet Enterprise in a context where the Puppet task interface is sub-optimal (edge cases involving the certs directory , perhaps), I would like to query PuppetDB for a list of nodes to run an ad-hoc task against. Today, such functionality can be accomplished using something like this:{{curl -X GET http://puppetdb.mydomain.edu:8080/v3/facts/fqdn | jq '.[] | .value' | sed 's/"//g' > target_nodes.txt}}Alternately, it may make more sense to query a Puppet infrastructure for managed nodes (e.g. those with a signed and un-revoked certificate)
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-8604) Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8604 Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet Change By: Henrik Lindberg Fix Version/s: PUP 6.0.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 (PUP-8761) Make convert_to() function accept additional arguments
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8761 Make convert_to() function accept additional arguments Change By: Henrik Lindberg Component/s: Type System Component/s: Functions 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Stefan Andres assigned an issue to Unassigned Puppet / PUP-8887 puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Change By: Stefan Andres Assignee: Stefan Andres 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title
Stefan Andres updated an issue
Puppet / PUP-8887
puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Change By:
Stefan Andres
*Puppet Version: 5.5.1*We are using array-iteration in our hiera.yaml to implement some kind of roles-concept.For this we have nodes that can define an array of roles.Those roles will be added to the hiera hierarchy by using the mapped_paths. The %\{roles} variable is defined in our site.pp by using the lookup() function.Prior to 5.5.1 we could could define lookup_options in roles dynamically loaded roles and define merge behavior or hashes defined in thoses roles. With 5.5.1 this does not seem to work anylonger. Values can still be looked up though. Below is a minimal reproducible case:{code:java} root@c312a1b640ef:/etc/puppetlabs/code/environments/production/manifests# cat ../hiera.yaml---version: 5defaults:hierarchy: - name: "node"path: node.yaml - name: "roles"mapped_paths: - roles - role - "%{role}.yaml" - name: "Other YAML hierarchy levels"paths: - "common.yaml" root@c312a1b640ef:/etc/puppetlabs/code/environments/production/manifests# cat ../data/ node.yamlroles: - firstrole - secondroleroot@c312a1b640ef:/etc/puppetlabs/code/environments/production/manifests# cat ../data/ common.yamlmyhash: key1: value1 key2: value2 root@c312a1b640ef:/etc/puppetlabs/code/environments/production/manifests# cat ../data/firstrole.yamllookup_options: myhash:merge: strategy: deepmyhash: role1: value1 role2: value2 role1: role1 root@c312a1b640ef:/etc/puppetlabs/code/environments/production/manifests# cat ../data/secondrole.yamlmyhash: role1: value1 role3: value3 role2: role2root@c312a1b640ef:/etc/puppetlabs/code/environments/production/manifests# cat site.pp$roles = lookup( 'roles', Array[String], 'unique', [], )notice("roles: $roles")$ret = lookup('myhash')notice("myhash: $ret")$role1 = lookup('role1')$role2 = lookup('role2')notice("role1 var: $role1")notice("role2 var: $role2")puppet-agent-5.4.0:root@c312a1b640ef:/etc/puppetlabs/code/environments/production/manifests# puppet apply site.ppWarning: Undefined variable 'roles'; \n (file & line not available)Notice: Scope(Class[main]): roles: [firstrole, secondrole]Notice: Scope(Class[main]): myhash: {key1 => value1, key2 => value2, role1 => value1, role3 => value3, role2 => value2}Notice: Scope(Class[main]): role1 var: role1Notice: Scope(Class[main]): role2 var: role2Notice: Compiled catalog for c312a1b640ef in environment production in 0.03 secondsNotice: Applied catalog in 0.01 secondspuppet-agent-5.5.1root@c312a1b640ef:/etc/puppetlabs/code/environments/production/manifests# puppet apply site.ppWarning: Undefined variable 'roles'; \n (file & line not available)Notice: Scope(Class[main]): roles: [firstrole, secondrole]Notice: Scope(Class[main]): myhash: {role1 => value1, role2 => value2}Notice: Scope(Class[main]): role1 var: role1Notice: Scope(Class[main]): role2 var: role2Notice: Compiled catalog for c312a1b640ef
Jira (BOLT-542) It should be easy to query PuppetDB with Bolt
Title: Message Title Paul Anderson created an issue Puppet Task Runner / BOLT-542 It should be easy to query PuppetDB with Bolt Issue Type: Improvement Assignee: Unassigned Created: 2018/05/24 7:19 AM Priority: Normal Reporter: Paul Anderson As a system administrator using Open Source Puppet, or Puppet Enterprise in a context where the Puppet task interface is sub-optimal, I would like to query PuppetDB for a list of nodes to run an ad-hoc task against. Today, such functionality can be accomplished using something like this: curl -X GET http://puppetdb.mydomain.edu:8080/v3/facts/fqdn | jq '.[] | .value' | sed 's/"//g' > target_nodes.txt Alternately, it may make more sense to query a Puppet infrastructure for managed nodes (e.g. those with a signed and un-revoked certificate) Add Comment
Jira (PUP-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Stefan Andres commented on PUP-8887 Re: puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Ah, I forgot to paste the node.yaml, of course - this is where our roles for nodes are defined: root@c312a1b640ef:/etc/puppetlabs/code/environments/production# cat data/node.yaml roles: - firstrole - secondrole Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Henrik Lindberg assigned an issue to Stefan Andres Puppet / PUP-8887 puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Change By: Henrik Lindberg Assignee: Thomas Hallgren Stefan Andres 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-8887 Re: puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml The example seems incomplete. I don't understand how the above code can produce the notice: roles: [firstrole, secondrole] Where did that array come from? Lookup will not find a 'roles' key in any of the listed data files and the provided default value is an empty array. I get the impression that $roles gets its value from a lookup and then is used to actually configure lookup. If that's true, then it's classic chicken-and-egg problem. Constructs like that should be avoided at length. 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
Jira (PUP-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8887 puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Change By: Henrik Lindberg Assignee: Thomas Hallgren Sub-team: Language Team: Platform Core 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8887 puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Change By: Henrik Lindberg Affects Version/s: PUP 5.5.1 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Stefan Andres commented on PUP-8887 Re: puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml The commit that introduced this new behavior is https://github.com/puppetlabs/puppet/commit/36cb716a37e091215ea5f2f9cdb8a29bff11e7b5#diff-9b5fcadd98b4a6f7f471fc1a8d3186dc in the file lib/puppet/pops/lookup/lookup_adapter.rb. When using an a revision older it still works. 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Stefan Andres commented on PUP-8887 Re: puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml With PUP-8715, this prevents us from upgrading the puppet-agents on our puppetservers (this is where the logic is only used) to puppet-agent-5.5.1. 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title
Stefan Andres created an issue
Puppet / PUP-8887
puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/05/24 2:29 AM
Priority:
Normal
Reporter:
Stefan Andres
Puppet Version: 5.5.1 We are using array-iteration in our hiera.yaml to implement some kind of roles-concept. For this we have nodes that can define an array of roles. Those roles will be added to the hiera hierarchy by using the mapped_paths. The %{roles} variable is defined in our site.pp by using the lookup() function. Prior to 5.5.1 we could could define lookup_options in roles dynamically loaded roles and define merge behavior or hashes defined in thoses roles. With 5.5.1 this does not seem to work anylonger. Values can still be looked up though. Below is a minimal reproducible case:
root@c312a1b640ef:/etc/puppetlabs/code/environments/production/manifests# cat ../hiera.yaml
---
version: 5
defaults:
hierarchy:
Jira (PUP-7822) Add a get() function that supports dot syntax to "dig" into hash/array
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7822
Add a get() function that supports dot syntax to "dig" into hash/array
Change By:
Henrik Lindberg
Release Notes Summary:
It is now possible to use the same "dot notation" to dig out a value from a structure like in hiera/lookup and elsewhere in puppet. To support this, the {{getvar()}} function has moved from stdlib to puppet, and we have added a new function {{get()}}. You can now for example use {{getvar('facts.os.family')}} starting with the variable name. The {{get}} function is the general function which takes a value and a dot-notation string.
Release Notes:
New Feature
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
