Jira (PUP-11604) "puppet module list --render-as json" does not report unmet dependencies
Title: Message Title
Chris Tessmer created an issue
Puppet / PUP-11604
"puppet module list --render-as json" does not report unmet dependencies
Issue Type:
Bug
Affects Versions:
PUP 7.17.0
Assignee:
Unassigned
Components:
PMT
Created:
2022/08/08 11:50 AM
Labels:
puppet rendering faces
Priority:
Normal
Reporter:
Chris Tessmer
Puppet Version: 7.18.0 Puppet Server Version: N/A OS Name/Version: N/A Running puppet module list will report unmet dependencies on the console, but this information is missing when run with --render-as json. Desired Behavior:{}
bpuppet module list --render-as json | jq keys
[
Jira (PDOC-226) Support for Type Aliases
Title: Message Title Chris Tessmer commented on PDOC-226 Re: Support for Type Aliases Just passing through and noticed this ticket―documentation for Type aliases have been implemented for a while: Example documentation generated from a simple Type Aliases: https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/REFERENCE.md#stdlibcompatbool Example documentation generated from a complex Type Alias (e.g., "not as much an alias as a type definition"): https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/REFERENCE.md#stdlibfilesource Not sure if local type aliases are handled or not; the few times I've seen local_types in the wild didn't have their own comments. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.239414.1520027126000.114557.1629761880189%40Atlassian.JIRA.
Jira (HI-622) Hiera/Lookup should emit warning about keys with malformed namespaces
Title: Message Title Chris Tessmer updated an issue Hiera / HI-622 Hiera/Lookup should emit warning about keys with malformed namespaces Change By: Chris Tessmer Summary: Hiera/Lookup should warn when encountering emit warning about keys with malformed namespaces Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390573.1615409101000.162825.1615409280031%40Atlassian.JIRA.
Jira (HI-622) Hiera/Lookup should warn when encountering keys with namespaces
Title: Message Title Chris Tessmer created an issue Hiera / HI-622 Hiera/Lookup should warn when encountering keys with namespaces Issue Type: New Feature Assignee: Unassigned Components: CLI, UX Created: 2021/03/10 12:45 PM Priority: Normal Reporter: Chris Tessmer A common (but hard-for-humans-to-spot) typo in Hiera data is namespacing parameters with a single colon instead of a two, like: mod_name::ns1::ns2:parameter: value instead of: mod_name::ns1::ns2::parameter: value It could save the industry a lot of collective time and head-scratching if Hiera or `puppet module lookup --explain` could emit a warning when encountering any key name that contains a single colon (:) instead of a double colon (::).
Jira (PDOC-152) Strings should support the documentation of private classes
Title: Message Title
Chris Tessmer commented on PDOC-152
Re: Strings should support the documentation of private classes
As a >3 year update to this discussion:
{{}}@api private has been available in Strings for some time to mark "module elements" like classes as private
PUP-523 was just transitioned from "Designing" back to "Open," so the introduction of a protected keyword seems unlikely in the foreseeable future.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.165906.1481479917000.55781.1588781280184%40Atlassian.JIRA.
Jira (PUP-1526) Package type should support environment variables
Title: Message Title Chris Tessmer commented on PUP-1526 Re: Package type should support environment variables The fix in PR #4928 (for Puppet 4.x) seemed close to getting accepted at one point, but it was eventually closed on 24 Oct 2017 due to a lack of activity and bandwidth/time constraints. 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 (PDOC-153) There is no correct method for documenting class variables that are not parameters but are meant to be available.
Title: Message Title Chris Tessmer commented on PDOC-153 Re: There is no correct method for documenting class variables that are not parameters but are meant to be available. I think the inability to document $name bothers me the most―it's a required parameter in every define and ought to be documentable. 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-6211) Bad behavior of getvar() from stdlib when strict_variables is set to true
Title: Message Title Chris Tessmer commented on PUP-6211 Re: Bad behavior of getvar() from stdlib when strict_variables is set to true I'd like to add a +1 to returning Undef instead of the Error String. It could easily end up as the content of a class parameter without detection (unless you start validate_re()-ing your String parameters against '^Warning: Undefined variable', which feels even more wrong). Undef makes much more intuitive sense as a return value when the target variable is not defined (it is literally called "Undef"), even in strict mode. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-852) Add support for systemd and systemd_version facts
Title: Message Title Chris Tessmer commented on FACT-852 Re: Add support for systemd and systemd_version facts it would be more flexible to provide the identity of the init system, instead of specifically testing for systemd. I would rather see something like $::osinitsystem, which would return a String like 'systemd', 'sysv-init', or 'upstart'. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3908) Tidy type is too verbose when working of directories containing lot of files
Title: Message Title Chris Tessmer commented on PUP-3908 Re: Tidy type is too verbose when working of directories containing lot of files PR: https://github.com/puppetlabs/puppet/pull/3693 This incorporates improvements suggested in the discussion thread at https://github.com/puppetlabs/puppet/pull/3518. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
