Jira (PUP-1329) composite namevars should be more robust

Edwin Wiles (JIRA) Mon, 15 Jan 2018 20:03:15 -0800

Title: Message Title

Edwin Wiles commented on

PUP-1329

I will admit that I have no idea how to solve this, but it does need some sort of solution.

If we cannot use title_patterns and "name" namevar at the same time, then there needs to be a published workaround, referenced from this ticket.

I did have one thought for a workaround, but I don't know enough about ruby, or puppet, to know how to make it work. What follows is a bit of pseudo-code to at least try to get the idea across.

newproperty(:parta, namevar: true) do

end

newproperty(:partb, namevar: true) do

end

newproperty(:partc, namevar: true) do

end

newproperty(:name, namevar: true) do

  validate do |value|

    if value.match(%r{(some)/(pattern)/(here)})

      set(:parta,$1)

      set(:partb,$2)

      set(:partc,$3)

    else

      raise Puppet::Error, "Pseudo title_pattern does not match."

end

end

end

Add Comment

This message was sent by Atlassian JIRA

--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-1329) composite namevars should be more robust

Reply via email to