Jira (PUP-10491) Allow adding descriptive or administrative information to resources

[Reid Vandewiele (Jira)]

Title: Message Title

Reid Vandewiele commented on PUP-10491   Re: Allow adding descriptive or administrative information to resources Josh Cooper I put a note out to puppet-dev on May 14, 2020, here: https://groups.google.com/g/puppet-dev/c/cDCyp_U8Sv0/m/FiN1EqxWAwAJ. No responses or commentary in that forum. What else needs to happen to move this ticket forward?   Henrik Lindberg that's a good consideration. Type validation is a powerful feature, provides some compelling benefits, and that idea inspires the example below. However, I think use of types needs to be optional, not something that could act as a barrier to entry. To be most useful, annotations need to be very, very easy to use. Users who want type validation could adopt this pattern: type OurOrg::Annotation = Struct[Optional[owner] => String[1], Optional[department] => Enum[operations, support, engineering]]   notify { 'example': annotation => OurOrg::Annotation({'owner' => 'Riley'}) }  In the proposed implementation, the metaparameter is validated by a type already (Data). If this is a compelling adjustment, we could choose someday to make that configurable. E.g. annotation_assert_type = Data # default; could set to OurOrg::Annotation instead However, for now I think the code would be clearest by requiring a self-evident pattern like the example. (Raw types as values would be similarly self-evident, but wouldn't be easy enough to use.) Add Comment   This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357687.1588699805000.134353.1632171480030%40Atlassian.JIRA.