Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-7885

Enum accepts arguments that are not strings

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 5.2.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Platform Core
    • Story Points:
      1
    • Sprint:
      Platform Core 2017-09-05
    • Method Found:
      Manual Test
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      It was in some circumstances possible to create an illegal specification of an Enum data type by giving in numeric entries instead of string entries - for example {{Enum\[blue, 42]}}. This illegal Enum type would then either cause an error when attempting to use it, or would have undefined matching behavior. This is now corrected so that an error is raised where this illegal specification was earlier accepted.
      Show
      It was in some circumstances possible to create an illegal specification of an Enum data type by giving in numeric entries instead of string entries - for example {{Enum\[blue, 42]}}. This illegal Enum type would then either cause an error when attempting to use it, or would have undefined matching behavior. This is now corrected so that an error is raised where this illegal specification was earlier accepted.
    • QA Risk Assessment:
      No Action

      Description

      "Enum[foo, 1]" parses in ruby but not in java
      com.puppet.pcore.TypeResolverException: Invalid parameter type specified: 'Enum' requires parameter 1 to be a 'String', Long provided

      I don't how important this is.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            alex Alex Dreyer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support