-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
config_hash converts strings to integers => breaks port mappings #119
Comments
Yea, we explicitly try to "cast" these into ints for service: Then we do it on a bit more keys here: I'm... up for suggestions? We could take a advantage of the fact that we have a custom function to write the json down: In ruby we could look at each key, and if it looks like an int, make it an int? |
Something like this?
|
Yea, that looks like it achieves the desired effect. |
@weitzj this should be fixed on the latest master thanks to @aj-jester |
Thank you. :) |
In the consul config_hash it is possible to disable the http port by setting it to
-1
, and enabling the https service instead by setting it to the appropiate port,8500
:The generated
config.json
results in:Current behaviour (Release 1.0.0)
-1
is looking good, and is still an integer, whilst the https ports was converted to a string. The consul agent does not support strings as port numbers and therefore fails to launch.Expected behaviour
-1
as well as8500
should be integers.Workaround
Tell puppet to treat "8500" as an integer by multiplying with
1 *
:The text was updated successfully, but these errors were encountered: