Jira (PUP-10025) puppet describe does not show top-level docs

27 views
Skip to first unread message

David Schmitt (JIRA)

unread,
Sep 19, 2019, 6:53:03 AM9/19/19
to puppe...@googlegroups.com
David Schmitt moved an issue
 
Puppet / Bug PUP-10025
puppet describe does not show top-level docs
Change By: David Schmitt
Key: PDK PUP - 945 10025
Project: Puppet Development Kit
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

David Schmitt (JIRA)

unread,
Sep 19, 2019, 7:38:03 AM9/19/19
to puppe...@googlegroups.com
David Schmitt updated an issue
Change By: David Schmitt
Affects Version/s: PUP 6.9.0
Affects Version/s: PUP 5.5.16

David Schmitt (JIRA)

unread,
Sep 19, 2019, 7:39:02 AM9/19/19
to puppe...@googlegroups.com

David Schmitt (JIRA)

unread,
Sep 19, 2019, 7:40:04 AM9/19/19
to puppe...@googlegroups.com
David Schmitt updated an issue
Change By: David Schmitt
Team: Network Automation

Jorie Tappa (JIRA)

unread,
Sep 23, 2019, 1:24:03 PM9/23/19
to puppe...@googlegroups.com
Jorie Tappa updated an issue
Change By: Jorie Tappa
Team: Coremunity

Jorie Tappa (JIRA)

unread,
Sep 23, 2019, 1:24:04 PM9/23/19
to puppe...@googlegroups.com
Jorie Tappa updated an issue
Change By: Jorie Tappa
Sprint: Coremunity Grooming

Josh Cooper (JIRA)

unread,
Nov 18, 2019, 12:36:04 PM11/18/19
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-10025
 
Re: puppet describe does not show top-level docs

This might be because puppet requires the top level description to end with a ".", see PUP-2641

David Schmitt (JIRA)

unread,
Nov 18, 2019, 1:26:05 PM11/18/19
to puppe...@googlegroups.com

PUP-2641 does not happen in 6.10.1 anymore (I've manually removed the last "." from the java_ks type to test):

david@davids:~/git/puppetlabs-java_ks$ bundle exec puppet describe --libdir ./lib java_ks | head
 
java_ks
=======
Manages the entries in a java keystore, and uses composite namevars to
accomplish the same alias spread across multiple target keystores
 
 
Parameters
----------
 
david@davids:~/git/puppetlabs-java_ks$ puppet --version
6.10.1
david@davids:~/git/puppetlabs-java_ks$ git describe --all --long
heads/master-0-gee1531a
david@davids:~/git/puppetlabs-java_ks$ 

and even with a dot at the end of the description (https://github.com/puppetlabs/puppetlabs-panos/blob/7f99a79294ab6601af3d1c3069712e604e85ad13/lib/puppet/type/panos_nat_policy.rb#L6) puppet describe still fails with this panos type:

david@davids:~/git/puppetlabs-panos$ bundle exec puppet describe panos_nat_policy --libdir ./lib | head
 
panos_nat_policy
================
 
 
 
Parameters
----------
 
- **bi_directional**
david@davids:~/git/puppetlabs-panos$ puppet --version
6.10.1
david@davids:~/git/puppetlabs-panos$ git describe --all --long
heads/master-0-g7f99a79
david@davids:~/git/puppetlabs-panos$ 

That got me thinking, and now there is a bugfix at https://github.com/puppetlabs/puppet-resource_api/pull/247/ .

Josh Cooper (JIRA)

unread,
Nov 18, 2019, 2:08:04 PM11/18/19
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-10025

I can reproduce 2641 using the rcsrepo example. Maybe there is difference in behavior with single vs multiline description/summaries?

Josh Cooper (JIRA)

unread,
Nov 18, 2019, 2:09:05 PM11/18/19
to puppe...@googlegroups.com
Josh Cooper updated an issue
 
Change By: Josh Cooper
Labels: beginner

David Schmitt (JIRA)

unread,
Nov 19, 2019, 11:39:06 AM11/19/19
to puppe...@googlegroups.com

David Schmitt (JIRA)

unread,
Nov 21, 2019, 8:50:04 AM11/21/19
to puppe...@googlegroups.com
David Schmitt updated an issue
 
Change By: David Schmitt
Fix Version/s: PUP 6.y

Josh Cooper (Jira)

unread,
Aug 3, 2021, 6:13:04 PM8/3/21
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Sprint: Community PRs
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Atlassian logo

Josh Cooper (Jira)

unread,
Aug 3, 2021, 6:13:04 PM8/3/21
to puppe...@googlegroups.com

Josh Cooper (Jira)

unread,
Aug 3, 2021, 6:14:04 PM8/3/21
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages