Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

Add your comments directly to the page. Include links to any relevant research, data, or feedback.

StatusIN PROGRESS
Impact

HIGH / MEDIUM / LOW

DriverTrevor Vaughan 
Approver
ContributorsLiz Nemsick Dylan Cochran (Unlicensed) Brandon Riden (Unlicensed) Kendall Moore Nick Markowski Nick Miller Judith Johnson Shark Bruhaha Jeanne Greulich Michael Morrone Chris Tessmer 
Informed
Due date
Outcome

Background

The MODULE-DATA epic is outdated and should not be done arbitrarily.

In general, the puppet community suggests using module data as appropriate and `params.pp` as appropriate.

Also, there has been no fix for the fact that even default data with no logic paths cannot be handled by `puppet strings` which makes the migration of all default data problematic for auto-generating documentation that is actually useful to end users.

Relevant data

Of the items in the table below, I believe that all can be closed except for SIMP-3281 which seems like a useful linting addition (but may already be completed)

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

Options considered


Option 1:Option 2:
DescriptionRemove all open items besides SIMP-3218Retain all open items and triage individually
Pros and cons

(plus) Allows natural migration to module data as appropriate

(minus) None

(plus) Allows for full analysis of each remaining module

(minus) Will probably camp on the backlog without resolution as it already has

Estimated costLOWMEDIUM

Action items

  •  

Outcome


  • No labels