Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
vicinus opened this issue Apr 4, 2024 · 1 comment

Comments

@vicinus
Copy link

vicinus commented Apr 4, 2024

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',
}
@fr-rin
Copy link

fr-rin commented Aug 20, 2024

I can confirm this issue.

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

No branches or pull requests

3 participants