Jira (PUP-9718) Create a plan_information_service in Puppet and add it to the information_service

0 views
Skip to first unread message

Branan Riley (JIRA)

unread,
May 22, 2019, 4:55:09 PM5/22/19
to puppe...@googlegroups.com
Branan Riley created an issue
 
Puppet / Task PUP-9718
Create a plan_information_service in Puppet and add it to the information_service
Issue Type: Task Task
Assignee: Unassigned
Created: 2019/05/22 1:54 PM
Priority: Normal Normal
Reporter: Branan Riley

The puppet information service is what puppetserver uses to ask Puppet about things stored in modules - currently classes and tasks, but it will need to be extended to support plans.

The example bits for tasks that this will be based on are

Note that because a plan will not have multiple files/implementations (as a task can) and has no standalone metadata file, it will be much easier to implement this for plans.

Plans do not have "metadata" per se, but we should populate the plan_data endpoint anyway, the parameters for the plan. We don't have a use for parameter data yet (it will be used to move parameter validation of plan calls earlier in the process), so if it ends up being complicated we can simply return empty metadata and create a new ticket associated with the work to validate parameters early.

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

Branan Riley (JIRA)

unread,
May 22, 2019, 5:06:02 PM5/22/19
to puppe...@googlegroups.com
Branan Riley updated an issue
Change By: Branan Riley
The puppet information service is what puppetserver uses to ask Puppet about things stored in modules - currently classes and tasks, but it will need to be extended to support plans.

The example bits for tasks that this will be based on are


Note that because a plan will not have multiple files/implementations (as a task can) and has no standalone metadata file, it will be much easier to implement this for plans.

Plans do not have "metadata" per se, but we should populate the {{plan_data}} endpoint anyway , with the parameters for the plan. We don't have a use for parameter data *yet* (it will be used to move parameter validation of plan calls earlier in the process), so if it ends up being complicated we can simply return empty metadata and create a new ticket associated with the work to validate parameters early.

Branan Riley (JIRA)

unread,
May 22, 2019, 5:22:03 PM5/22/19
to puppe...@googlegroups.com

Branan Riley (JIRA)

unread,
May 22, 2019, 5:28:03 PM5/22/19
to puppe...@googlegroups.com

Branan Riley (JIRA)

unread,
May 22, 2019, 5:28:03 PM5/22/19
to puppe...@googlegroups.com

Scott McClellan (JIRA)

unread,
May 24, 2019, 1:02:04 PM5/24/19
to puppe...@googlegroups.com

Branan Riley (JIRA)

unread,
Jun 5, 2019, 2:12:05 PM6/5/19
to puppe...@googlegroups.com
Branan Riley updated an issue
Change By: Branan Riley
Sprint: Skeletor Kanban 20190605 , Skeletor Kanban 20190619

Geoff Nichols (JIRA)

unread,
Jun 19, 2019, 2:19:04 PM6/19/19
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Sprint: Skeletor Kanban 20190605, Skeletor Kanban 20190619 , Skeletor Kanban 20190703

Scott McClellan (JIRA)

unread,
Jun 27, 2019, 5:10:03 PM6/27/19
to puppe...@googlegroups.com

Scott McClellan (JIRA)

unread,
Jun 27, 2019, 5:22:03 PM6/27/19
to puppe...@googlegroups.com
Scott McClellan updated an issue
Change By: Scott McClellan
Fix Version/s: PUP 6.y
Fix Version/s: PUP 6.6.0

Scott McClellan (JIRA)

unread,
Jun 27, 2019, 5:22:03 PM6/27/19
to puppe...@googlegroups.com

Geoff Nichols (JIRA)

unread,
Jul 1, 2019, 3:50:02 PM7/1/19
to puppe...@googlegroups.com
Geoff Nichols commented on New Feature PUP-9718
 
Re: Create a plan_information_service in Puppet and add it to the information_service

I don't see this commit in the puppet 6.6.0 tag, removing the PUP 6.6.0 Fix Version.

Geoff Nichols (JIRA)

unread,
Jul 1, 2019, 3:50:03 PM7/1/19
to puppe...@googlegroups.com
Geoff Nichols updated an issue
 
Change By: Geoff Nichols
Fix Version/s: PUP 6.6.0
Fix Version/s: PUP 6.7.0
Reply all
Reply to author
Forward
0 new messages