Jira (FACT-1753) Update facter tests to support SLES 12 Power8 platform
Title: Message Title Scott Garman created an issue Facter / FACT-1753 Update facter tests to support SLES 12 Power8 platform Issue Type: Task Assignee: Scott Garman Created: 2017/09/14 4:53 PM Priority: Normal Reporter: Scott Garman The sles fact acceptance test needs to be updated to work when run against a SLES 12 Power8 server. Specifically the os_arch and kernel_version checks. There is prior art you can compare this to in the EL fact acceptance test. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-5454) Bind mounts are not correctly handled by the 'mount' provider.
Title: Message Title Trevor Vaughan commented on PUP-5454 Re: Bind mounts are not correctly handled by the 'mount' provider. Owen Rodabaugh Well, technically everything has a workaround using exec , but That said, I guess an OK short term bespoke workaround would be OK. Anyone using NFSv4 will probably be using Puppet to manage bind mounts at some point. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-2487 Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: This impacts mostly large customers or those which run everything in noop. This inflates the size of the table in PDB which can use up disk space and grow the table to a size where the queries from event inspector no longer complete.There is a terrible workaround using a cron job with a delete statement directly against this table. CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-5454) Bind mounts are not correctly handled by the 'mount' provider.
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-5454 Bind mounts are not correctly handled by the 'mount' provider. Change By: Owen Rodabaugh CS Priority: Needs Priority Minor CS Impact: This is a rare issue because not many people manage bind mounts with puppet. It has a workaround using execs. CS Severity: 3 - Serious CS Business Value: 2 - $$$ CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received
Jira (PUP-4755) Puppet config set --section main foo bar does not set or respect an empty [main] section
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-4755 Puppet config set --section main foo bar does not set or respect an empty [main] section Change By: Adrien Thebo Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6802) Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-6802 Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment Change By: Owen Rodabaugh CS Priority: Major CS Impact: Similar impact as PUP-6739 CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 4 - 50-90% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because
Jira (PUP-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Adrien Thebo Assignee: Patrick Carlisle Adrien Thebo Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4755) Puppet config set --section main foo bar does not set or respect an empty [main] section
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-4755 Puppet config set --section main foo bar does not set or respect an empty [main] section Change By: Adrien Thebo Assignee: Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-6739 Error running puppet with non-existent and non-default environment Change By: Owen Rodabaugh CS Priority: Needs Priority Major CS Impact: While this issue isn't difficult for an experienced user to work around. For many new or non-english reading users the error may not be easily understood and breaks CLI usage of puppet on the node. CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 4 - 50-90% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Adrien Thebo Sprint: AP 2017-01-11, AP 2017-03-08, Agent 2017-03-22, Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-582) Make hiera.yaml aware of key
Title: Message Title Laura Macchi commented on HI-582 Re: Make hiera.yaml aware of key Awesome, thanks Henrik and Craig! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Adrien Thebo commented on PUP-6986 Re: Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars PR is currently targeted at 4.10.x; I'm inquiring into whether we can retarget it at master to make the merge easier to justify. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Adrien Thebo Assignee: Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7844) A Puppet report from an interrupted run can cause exit_status to throw an exception
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7844 A Puppet report from an interrupted run can cause exit_status to throw an exception Change By: Adrien Thebo Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-582) Make hiera.yaml aware of key
Title: Message Title Henrik Lindberg commented on HI-582 Re: Make hiera.yaml aware of key Laura Macchi I chatted with Craig about this, he has already fixed the very same problem in his HTTP backend and he said he will do the same fix for his mysql backend. He also promised to post on this ticket with info when he has a fix for the problem. So... stay tuned. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7948) selmodversion_loaded lines variable broken
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-7948
selmodversion_loaded lines variable broken
Change By:
Eric Delaney
I was playing with rubocop when it complained about:{code}== lib/puppet/provider/selmodule/semodule.rb ==W:121: 13: Lint/EmptyExpression: Avoid empty expressions.{code}Looking at the code its complaining about the "lines = ()" assignment:{code} def selmodversion_loadedlines = ()begin execpipe("#{command(:semodule)} --list") do |output|output.each_line do |line| line.chomp! bits = line.split if bits[0] == @resource[:name]self.debug "load version #{bits[1]}"return bits[1] endend endrescue Puppet::ExecutionFailure raise Puppet::ExecutionFailure, "Could not list policy modules: #{lines.join(' ').chomp!}", $!.backtraceendnil end{code]Looking at the code, lines will be assigned "nil" which doesn't have a .join method. So the exception will fail. We also fail to do anything with the lines variable in the method so if it was intended to be an array, it never gets changed from an empty array which is kind of pointless. We should enable "Lint/EmptyExpression" in the .robocop.yml if when this is fixed and we're on 0.49 or greater.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post
Jira (PUP-7942) Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline
Title: Message Title Geoff Nichols commented on PUP-7942 Re: Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline Merged to ci-job-configs#master at https://github.com/puppetlabs/ci-job-configs/commit/6ce0b11f0aa2ca38be29f6d1b7d76be16cd59f57. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7942) Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline
Title: Message Title Geoff Nichols assigned an issue to Sean McDonald Puppet / PUP-7942 Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline Change By: Geoff Nichols Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7845) Support leaf certificate CRL checking
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7845 Support leaf certificate CRL checking Change By: Adrien Thebo Sprint: Platform Core 2017-08-22, Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3673) Rigorously enforce keyword validity on ingest, or normalize, or...
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3673 Rigorously enforce keyword validity on ingest, or normalize, or... Change By: Rob Browning Sprint: Data Platform Next Sprint Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3673) Rigorously enforce keyword validity on ingest, or normalize, or...
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3673 Rigorously enforce keyword validity on ingest, or normalize, or... Issue Type: Bug Assignee: Unassigned Created: 2017/09/14 12:24 PM Priority: Normal Reporter: Rob Browning Right now pdp will accept something like puppet-Container/id, and then be unable to find it in queries. Fix that somehow. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (HI-582) Make hiera.yaml aware of key
Title: Message Title Laura Macchi commented on HI-582 Re: Make hiera.yaml aware of key How do I provide a query like the ones described above? I am working on a mssql lookup_key function, and find it really hard to implement without hiera.yaml aware of key. Do you have any suggestions on how to implement that? I've noticed that Craig didn't write the MySQL backend in hiera 5, and the hiera 3 one stopped working, I'm guessing it is because of this? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Alexander Johnson updated an issue Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Alexander Johnson Labels: AWS1 backup-restore cstop10 the-goods Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-582) Make hiera.yaml aware of key
Title: Message Title
Henrik Lindberg commented on HI-582
Re: Make hiera.yaml aware of key
The way to implement this is to use a backend of the hiera5 lookup_key kind of backend function. It can receive the query and do whatever processing it wants. (Here is the documentation for the lookup key kind of backend: https://docs.puppet.com/puppet/5.1/hiera_custom_lookup_key.html). That however is something that is best implemented by the implementor of the backend ("crayfishx" - Craig Dunn).
I would be very hesitant to making the key being looked up available for interpolation as that completely blows up any caching (and therefore most of the performance gains in hiera 5) since the key changes with every lookup.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Geoff Nichols commented on PUP-7451 Re: Puppet HTTP client should respect Retry-After headers Merged to puppet#5.3.x at https://github.com/puppetlabs/puppet/commit/3ec7589fb2504715152ee8d555a4d5621721ff52. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Geoff Nichols Fix Version/s: PUP 5.y Fix Version/s: PUP 5.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1752) Add support for AIX LPAR and WPAR detection
Title: Message Title Casey Williams created an issue Facter / FACT-1752 Add support for AIX LPAR and WPAR detection Issue Type: Task Assignee: Casey Williams Created: 2017/09/14 10:51 AM Priority: Normal Reporter: Casey Williams Detect AIX's LPAR and WPAR environments. LPARs are possible on all supported AIX versions, but WPARs are only available on AIX 6.1+. For LPARs Iit seems that it will be sufficient to check that the output of lparstat -i reports a nonzero partition number. For WPARs, it looks like we'll need to check that lparstat -iW reports a nonzero WPAR key. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (HI-582) Make hiera.yaml aware of key
Title: Message Title
Ranjit Viswakumar updated an issue
Hiera / HI-582
Make hiera.yaml aware of key
Change By:
Ranjit Viswakumar
In the past, hiera.yaml was aware of {{"%\{key\}"}}, which allowed to write custom backends with options like this:{{:query: SELECT val FROM configdata WHERE var='%\{key\}'}}With hiera 5, hiera.yaml is not aware of key, so when that option gets to the function, it looks like:{{:query: SELECT val FROM configdata WHERE var=''}}Customers that use the [mysql backend](https://github.com/crayfishx/hiera-mysql), for example, cannot use it in hiera 5 and writing one without key relies on a very inflexible implementation , since the query needs to be hardcoded hard coded inside the function code.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-582) Make hiera.yaml aware of key
Title: Message Title
Ranjit Viswakumar updated an issue
Hiera / HI-582
Make hiera.yaml aware of key
Change By:
Ranjit Viswakumar
In the past, hiera.yaml was aware of {{"%\{key\}"}}, which allowed to write custom backends with options like this:{{:query: SELECT val FROM configdata WHERE var='%\{key\}'}}With hiera 5, hiera.yaml is not aware of key, so when that option gets to the function, it looks like:{{:query: SELECT val FROM configdata WHERE var=''}}Customers that use the [mysql backend](https://github.com/crayfishx/hiera-mysql), for example, cannot use it in hiera 5 and writing one without key relies in on a very inflexible implementation, since the query needs to be hardcoded inside the function code.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-582) Make hiera.yaml aware of key
Title: Message Title
Ranjit Viswakumar updated an issue
Hiera / HI-582
Make hiera.yaml aware of key
Change By:
Ranjit Viswakumar
In the past, hiera.yaml was aware of {{" % \ {key \ } "}} , which allowed to write custom backends with options like this: {{ :query: SELECT val FROM configdata WHERE var='% \ {key \ }' }} With hiera 5, hiera.yaml is not aware of key, so when that option gets to the function, it looks like: {{ :query: SELECT val FROM configdata WHERE var='' }} Customers that use the [mysql backend](https://github.com/crayfishx/hiera-mysql), for example, cannot use it in hiera 5 and writing one without key relies in a very inflexible implementation, since the query needs to be hardcoded inside the function code.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7894) Scheduled Task v2 - Create windows/taskscheduler2
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7894 Scheduled Task v2 - Create windows/taskscheduler2 Change By: Ethan Brown Fix Version/s: PUP 5.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-582) Make hiera.yaml aware of key
Title: Message Title
Laura Macchi updated an issue
Hiera / HI-582
Make hiera.yaml aware of key
Change By:
Laura Macchi
In the past, hiera.yaml was aware of %{key}, which allowed to write custom backends with options like this: {code} :query: SELECT val FROM configdata WHERE var='%{key}' {code} With hiera 5, hiera.yaml is not aware of key, so when that option gets to the function, it looks like: {code} :query: SELECT val FROM configdata WHERE var='' {code} Customers that use the [mysql backend](https://github.com/crayfishx/hiera-mysql), for example, cannot use it in hiera 5 and writing one without key relies in a very inflexible implementation, since the query needs to be hardcoded inside the function code.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-582) Make hiera.yaml aware of key
Title: Message Title
Laura Macchi created an issue
Hiera / HI-582
Make hiera.yaml aware of key
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/09/14 9:57 AM
Priority:
Normal
Reporter:
Laura Macchi
In the past, hiera.yaml was aware of % {key}, which allowed to write custom backends with options like this:
:query: SELECT val FROM configdata WHERE var='%{key}
'
With hiera 5, hiera.yaml is not aware of key, so when that option gets to the function, it looks like:
Jira (PUP-7950) Allow specifying an MD5 URI for files with HTTP(s) sources
Title: Message Title
Lee Lowder created an issue
Puppet / PUP-7950
Allow specifying an MD5 URI for files with HTTP(s) sources
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2017/09/14 9:03 AM
Priority:
Normal
Reporter:
Lee Lowder
Because a simple "touch" command can change the ctime/mtime on files, and thus leading to false changes (which could then trigger service or exec refreshes). there should be a way to specify a URI that contains an MD5sum or other checksum value for files that use http or https based sources.
Example:
file {
'/some/path/to/some_file.ext':
source => 'http:://example.com/files/some_file.ext',
checksum_source =>
Jira (FACT-1751) hypervisors fact is not blockable
Title: Message Title John Duarte updated an issue Facter / FACT-1751 hypervisors fact is not blockable Change By: John Duarte QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5302) composite namevar not taker into account in prefetch.
Title: Message Title Nick Hilhorst commented on PUP-5302 Re: composite namevar not taker into account in prefetch. Sofer, thanks for the workaround! I ran into the same problem and your solution helped me fix it. I don't think I could have figured this out myself. Especially how you use resources.values.first.catalog.resources to get the complete catalog with no items missing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
