Jira (PUP-11867) Documentation: default is now strict=error

6 views
Skip to first unread message

Daniel Parks (Jira)

unread,
Jun 4, 2023, 12:55:02 AM6/4/23
to puppe...@googlegroups.com
Daniel Parks created an issue
 
Puppet / Bug PUP-11867
Documentation: default is now strict=error
Issue Type: Bug Bug
Affects Versions: PUP 8.0.1, PUP 8.0.0
Assignee: Unassigned
Components: Docs
Created: 2023/06/03 9:54 PM
Priority: Normal Normal
Reporter: Daniel Parks

Puppet Version: 8.0.0
Puppet Server Version: N/A
OS Name/Version: N/A

The official documentation says that the default for the strict setting is warning, but the actual default is error.

I believe the documentation for strict_variables is also incorrect, but I haven’t run into it myself.

Unfortunately, this is very confusing, because it causes all warnings to become errors (I’m filing a separate issue about that). So, it’s particularly important that this documentation be correct.

Desired Behavior: Documentation has correct default for strict setting.
Actual Behavior: Documentation has incorrect default for strict setting.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Atlassian logo

Daniel Parks (Jira)

unread,
Jun 4, 2023, 1:09:02 AM6/4/23
to puppe...@googlegroups.com
Daniel Parks commented on Bug PUP-11867
 
Re: Documentation: default is now strict=error

I filed PUP-11868 about the new default breaking deprecation warnings.

Michael Hashizume (Jira)

unread,
Jun 5, 2023, 4:31:01 PM6/5/23
to puppe...@googlegroups.com

Michael Hashizume (Jira)

unread,
Jun 6, 2023, 4:19:01 PM6/6/23
to puppe...@googlegroups.com
Michael Hashizume assigned an issue to Parker Leach
Change By: Michael Hashizume
Assignee: Michael Hashizume Parker Leach

Michael Hashizume (Jira)

unread,
Jun 6, 2023, 4:19:02 PM6/6/23
to puppe...@googlegroups.com

Parker Leach (Jira)

unread,
Jun 20, 2023, 4:30:03 PM6/20/23
to puppe...@googlegroups.com
Parker Leach commented on Bug PUP-11867
 
Re: Documentation: default is now strict=error

Tony Vu This has been fixed- closing the ticket now.

Reply all
Reply to author
Forward
0 new messages