Skip to content

A port range is no longer allowed as a value at the "ports" parameter of the frontend resource #606

Description

@vicinus

Describe the Bug

Prior to the conversion of ERB to EPP templates in commit a32adb5 it was possible to add a port range to the "ports" parameter of the frontend resource. The reason this worked was that the rube to_i method ignores non integer endings (documentation: https://apidock.com/ruby/String/to_i)

Expected Behavior

As port ranges are valid in haproxy and worked in the past, the puppet ports parameter should support them again.

Steps to Reproduce

Steps to reproduce the behavior:

haproxy::frontend { 'test':
  ipaddress => '127.0.0.1',
  ports => '10000-10250',
}

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions