Jira (PDOC-249) Yardoc "Extra Files" Link doesn't display
Title: Message Title David Hollinger created an issue Puppet Strings / PDOC-249 Yardoc "Extra Files" Link doesn't display Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2018-05-15 at 2.50.48 PM.png, Screen Shot 2018-05-15 at 2.51.10 PM.png, Screen Shot 2018-05-15 at 3.31.29 PM.png Created: 2018/05/15 1:31 PM Priority: Normal Reporter: David Hollinger When using the yardoc Extra Files feature via .yardopts: --markup markdown --output-dir public - CHANGELOG.md docs/Overview.md Puppet Strings will still add the "extra files" to the
Jira (BOLT-461) Rename bolt package to puppet-bolt
Title: Message Title David Hollinger commented on BOLT-461 Re: Rename bolt package to puppet-bolt Kate Lopresti - is a package name change really a breaking change? It's somewhat broken/incompatible with certain systems as is due to the package name conflict. Even then, this change won't, in and of itself, change/break existing application functionality. If a package name change can be tagged as breaking because some users might do their own thing to automate installations, then potentially any change can be considered breaking due to how users may interact with the app within their own environments. 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 (PDB-3856) PQL specifying both type and title for class makes pql not find existing class
Title: Message Title David Hollinger commented on PDB-3856 Re: PQL specifying both type and title for class makes pql not find existing class foo was not my real query, no. It's entirely possible that it was my query, but I'll validate tonight. 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 (PDB-3856) PQL specifying both type and title for class makes pql not find existing class
Title: Message Title David Hollinger commented on PDB-3856 Re: PQL specifying both type and title for class makes pql not find existing class For us, this ticket is a bit more high priority as I have noticed that a downgrade of PuppetDB is not possible due to the changes to how Facts are stored. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3856) PQL specifying both type and title for class makes pql not find existing class
Title: Message Title
David Hollinger created an issue
PuppetDB / PDB-3856
PQL specifying both type and title for class makes pql not find existing class
Issue Type:
Bug
Affects Versions:
PDB 5.2.0
Assignee:
Unassigned
Created:
2018/02/26 1:35 PM
Priority:
Normal
Reporter:
David Hollinger
I noticed today when attempting to do a PQL query against the PuppetDB REST API to gather a list of nodes with a specific class assigned to it, that I get an empty array in return. When I execute:
$ curl -XGET http://localhost:8080/pdb/query/v4 --data-urlencode 'query=nodes[certname] { resources { title = "foo" } }'
I will get a list of nodes back that have ANY resources with title of "foo". When I execute:
$ curl -XGET http://localhost:8080/pdb/query/v4 --data-urlencode 'query=resources { type = "Class" and certname = "node" }'
Jira (PUP-8443) Hiera3 Lookups fail when agent 5.3.4 is installed
Title: Message Title David Hollinger updated an issue Puppet / PUP-8443 Hiera3 Lookups fail when agent 5.3.4 is installed Change By: David Hollinger Affects Version/s: PUP 5.3.4 Component/s: Hiera & Lookup Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-211) Support ssh through a jump box
Title: Message Title
David Hollinger updated an issue
Puppet Task Runner / BOLT-211
Support ssh through a jump box
Change By:
David Hollinger
In many environments users cannot ssh directly into their target nodes and need to ssh through a jump box to access the target. Bolt should support executing through a jumpbox.{quote=dhollinger} For example, if you normally ssh into a server using `ssh u...@node.example.com` but instead we have to use `ssh -p user@sshjump login node.example.com` {quote}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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-211) Support ssh through a jump box
Title: Message Title
David Hollinger updated an issue
Puppet Task Runner / BOLT-211
Support ssh through a jump box
Change By:
David Hollinger
In many environments users cannot ssh directly into their target nodes and need to ssh through a jump box to access the target. Bolt should support executing through a jumpbox.{quote =dhollinger }For example, if you normally ssh into a server using `ssh u...@node.example.com` but instead we have to use `ssh -p user@sshjump login node.example.com`{quote}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-179) Support Custom Ruby Fact documentation
Title: Message Title David Hollinger created an issue Puppet Strings / PDOC-179 Support Custom Ruby Fact documentation Issue Type: New Feature Assignee: Unassigned Components: DOCS Created: 2017/10/12 11:20 AM Priority: Normal Reporter: David Hollinger It would be nice to be able to generate puppet-strings docs for custom ruby facts as well. As of right now, documentation for any custom facts still has to live in the code comments or the README.md file. Add Comment
Jira (PUP-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title David Hollinger commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Josh Cooper, Any idea when such a fix might be pushed into the external gem and release. Right now this issue is preventing users of the VP metadata-json-lint tool from using Puppet 5 as it breaks puppet module install with the external gem and the metadata-json-lint gem is broken without the external gem. We're looking into workarounds on our end, but it'd be preferential to not have to hack together some crazy logic depending on Puppet version. 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-3587) puppetlabs-puppetdb : doesn't work with puppetlabs-postgresql 5.x
Title: Message Title David Hollinger commented on PDB-3587 Re: puppetlabs-puppetdb : doesn't work with puppetlabs-postgresql 5.x PR at https://github.com/puppetlabs/puppetlabs-puppetdb/pull/260 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-3587) puppetlabs-puppetdb : doesn't work with puppetlabs-postgresql 5.x
Title: Message Title
David Hollinger updated an issue
PuppetDB / PDB-3587
puppetlabs-puppetdb : doesn't work with puppetlabs-postgresql 5.x
Change By:
David Hollinger
_Basic Info_*Module Version:*_Describe your issue in as much detail as possible..._The puppetdb module currently pins on postgresql < 5.0.0, and now that 5.0.0 is out it is incompatible. https://github.com/puppetlabs/puppetlabs-puppetdb/blob/master/metadata.json#L81*Desired Behavior:*Installing a 5.x series of postgresql with puppetdb works.*Actual Behavior:*Puppet run fails with following error:{{ Error: Evaluation Error: Error while evaluating a Resource Statement, Postgresql::Server::Grant[database:GRANT puppetdb - all - puppetdb]: parameter 'port' expects an Integer value, got String at /etc/puppetlabs/code/environments/production/modules/postgresql/manifests/server/database_grant.pp:10 on node centos-7-x64}} Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.
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-3587) puppetlabs-puppetdb : doesn't work with puppetlabs-postgresql 5.x
Title: Message Title
David Hollinger updated an issue
PuppetDB / PDB-3587
puppetlabs-puppetdb : doesn't work with puppetlabs-postgresql 5.x
Change By:
David Hollinger
_Basic Info_*Module Version:*_Describe your issue in as much detail as possible..._The puppetdb module currently pins on postgresql < 5.0.0, and now that 5.0.0 is out it is incompatible. https://github.com/puppetlabs/puppetlabs-puppetdb/blob/master/metadata.json#L81*Desired Behavior:*Installing a 5.x series of postgresql with puppetdb works.*Actual Behavior:* [~dhollinger] can fill this in. Puppet run fails with following error: {{ Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.
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-3587) puppetlabs-puppetdb : doesn't work with puppetlabs-postgresql 5.x
Title: Message Title David Hollinger commented on PDB-3587 Re: puppetlabs-puppetdb : doesn't work with puppetlabs-postgresql 5.x Here is the error message I see in my beaker tests: Error: Evaluation Error: Error while evaluating a Resource Statement, Postgresql::Server::Grant[database:GRANT puppetdb - all - puppetdb]: parameter 'port' expects an Integer value, got String at /etc/puppetlabs/code/environments/production/modules/postgresql/manifests/server/database_grant.pp:10 on node centos-7-x64 Modules: puppetlabs-puppetdb 5.1.2 puppetlabs-postgresql 5.0.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 (PUP-1916) puppet cert clean cannot remove signing requests
Title: Message Title David Hollinger commented on PUP-1916 Re: puppet cert clean cannot remove signing requests Can we get this ticket updated to show that this effects puppetserver <= 2.7.2 and puppet <= 4.10.1? 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.
