Jira (PDB-2642) PQL: Spike/research deactivated node handling
Title: Message Title Daniel Parks commented on PDB-2642 Re: PQL: Spike/research deactivated node handling To be clear, this suggestion from Charlie Sharpsteen would be really helpful: Or go back to implicitly filtering results from deactivated nodes in all entities, but provide command line switches and API headers that can turn this implicit filter off. 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-2642) PQL: Spike/research deactivated node handling
Title: Message Title
Daniel Parks commented on PDB-2642
Re: PQL: Spike/research deactivated node handling
Please please please add a way to disable data from deactivated nodes.
I have never ever wanted to get data from a deactivated node, so I have to stick the nodes { deactivated is null and expired is null} somewhere in all my queries. It's really easy to forget, so I end up with results that don't make sense. It's an irritation every time I use PuppetDB.
I can't even fix it programmatically without a silly amount of effort (parse the PQL, add the deactivated subquery to each subquery, etc.).
An HTTP parameter would be wonderful.
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-3393) PQL: querying structured facts is awkward
Title: Message Title
Daniel Parks commented on PDB-3393
Re: PQL: querying structured facts is awkward
Also, this is ignoring what I have to do to filter out deactivated nodes:
facts[certname,value] {
name="classification"
and certname in inventory[certname] {
facts.classification.version = 1
and nodes { deactivated is null and expired is null }
}
}
Add Comment
Jira (PDB-3393) PQL: querying structured facts is awkward
Title: Message Title
Daniel Parks created an issue
PuppetDB / PDB-3393
PQL: querying structured facts is awkward
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2017/04/02 8:43 PM
Environment:
PE 2017.1.1
Priority:
Normal
Reporter:
Daniel Parks
If I want to query based on the content of a structured fact, I have to query the inventory. In order to retrieve just the value of the structured fact, I have to query facts and make a subquery to the inventory.
More generally, the syntax is inconsistent and the inconsistency doesn't make day-to-day tasks easier.
facts[certname,value] { name="classification" and certname in inventory[certname] { facts.classification.version = 1 } }
[{"certname": . . .}]
Jira (PUP-6373) SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6373 SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-7421) puppet lookup silently fails with corrupt hiera.yaml
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7421 puppet lookup silently fails with corrupt hiera.yaml Change By: Geoff Nichols Sprint: PDE Triage 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-7421) puppet lookup silently fails with corrupt hiera.yaml
Title: Message Title Geoff Nichols moved an issue Puppet / PUP-7421 puppet lookup silently fails with corrupt hiera.yaml Change By: Geoff Nichols Affects Version/s: puppet-agent 1.6.0 Key: PA PUP - 671 7421 Project: Puppet Agent 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-7420) Lookups are logged as both lookup and APL when using log-level debug
Title: Message Title Henrik Lindberg commented on PUP-7420 Re: Lookups are logged as both lookup and APL when using log-level debug While not critical, this is a fix that is valuable to get into 4.10.0 if possible since it removes a very irritating problem with debug output. Ping Kenn Hussey. 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-7418) Deep merge regression when a value of subkey is an alias or an hiera interpolation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7418 Deep merge regression when a value of subkey is an alias or an hiera interpolation Change By: Henrik Lindberg Release Notes Summary: The combination of a deep merge lookup and the use of an interpolation function in hiera data (alias, lookup, or hiera) could cause the deep merge to end without having performed a full search and silently produce a result where some values would be missing. This is now fixed. Release Notes: Bug Fix 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-7418) Deep merge regression when a value of subkey is an alias or an hiera interpolation
Title: Message Title Henrik Lindberg commented on PUP-7418 Re: Deep merge regression when a value of subkey is an alias or an hiera interpolation merged to stable at: 47baa27 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-7420) Lookups are logged as both lookup and APL when using log-level debug
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7420 Lookups are logged as both lookup and APL when using log-level debug Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-7420) Lookups are logged as both lookup and APL when using log-level debug
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7420 Lookups are logged as both lookup and APL when using log-level debug Issue Type: Bug Affects Versions: PUP 4.9.4 Assignee: Thomas Hallgren Created: 2017/04/02 3:31 AM Fix Versions: PUP 4.10.z Priority: Normal Reporter: Thomas Hallgren When using log-level debug, a call to lookup will output the information from the lookup explainer. This happens twice when the lookup originates from a call to the lookup function. The second time, the lookup appears to be an APL (Automatic Parameter Lookup). Add Comment
Jira (PUP-7418) Deep merge regression when a value of subkey is an alias or an hiera interpolation
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7418 Deep merge regression when a value of subkey is an alias or an hiera interpolation Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-7418) Deep merge regression when a value of subkey is an alias or an hiera interpolation
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7418 Deep merge regression when a value of subkey is an alias or an hiera interpolation Change By: Thomas Hallgren Story Points: 1 Sprint: PDE 2017-04-05 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.
