Jira (PUP-8587) Rich Data support (Binary and others) in Puppet 6.y

2 views
Skip to first unread message

Henrik Lindberg (JIRA)

unread,
Mar 22, 2018, 1:35:02 PM3/22/18
to puppe...@googlegroups.com
Henrik Lindberg created an issue
 
Puppet / Epic PUP-8587
Rich Data support (Binary and others) in Puppet 6.y
Issue Type: Epic Epic
Assignee: Unassigned
Created: 2018/03/22 10:34 AM
Priority: Normal Normal
Reporter: Henrik Lindberg

This is an epic for support of Rich Data in the Catalog for the purpose of supporting primarily the Binary data type and new features for late binding values.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Henrik Lindberg (JIRA)

unread,
Mar 22, 2018, 1:35:04 PM3/22/18
to puppe...@googlegroups.com

Kenn Hussey (JIRA)

unread,
Mar 22, 2018, 2:04:05 PM3/22/18
to puppe...@googlegroups.com
Kenn Hussey updated an issue
Change By: Kenn Hussey
Priority: Normal Critical

Maggie Dreyer (JIRA)

unread,
Jun 20, 2018, 12:05:04 PM6/20/18
to puppe...@googlegroups.com

Scott Garman (JIRA)

unread,
Sep 18, 2018, 11:25:03 AM9/18/18
to puppe...@googlegroups.com
Scott Garman updated an issue
Change By: Scott Garman
Fix Version/s: PUP 6.0.0
Fix Version/s: PUP 6.y

Josh Cooper (JIRA)

unread,
Apr 17, 2019, 4:33:02 PM4/17/19
to puppe...@googlegroups.com

Henrik Lindberg (JIRA)

unread,
Apr 19, 2019, 7:02:04 AM4/19/19
to puppe...@googlegroups.com

The status of the tickets in this Epic looks correct to me except possibly PUP-8602. The basic feature is in place as we can send rich data in a catalog, and we can handle them in reports (even though we drop some of the rich data information).

Since to Puppet Language code is plugin-synced and data type aliases defined this way are not available on agents.
The ticket PUP-8621 is a nice to have that could be taken out of this epic.

I think we can close this epic and move the remaining tickets elsewhere.

Eric Thompson (JIRA)

unread,
Jul 25, 2019, 7:38:02 PM7/25/19
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages