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.

Sign up for GitHub

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

Jump to bottom

retry_interval should be a string #244

Closed
Chili-Man opened this issue Dec 2, 2015 · 3 comments
Closed

retry_interval should be a string #244

Chili-Man opened this issue Dec 2, 2015 · 3 comments

Comments

@Chili-Man
Copy link

The consul agent expects the retry_interval setting to be a string, but the consul_config lwrp wants it to be an integer: https://github.com/johnbellone/consul-cookbook/blob/master/libraries/consul_config.rb#L75

* 'retry_interval' expected type 'string', got unconvertible type 'float64'
==> Error decoding '/etc/consul.json': 1 error(s) decoding:
@johnbellone
Copy link
Contributor

Do you mind submitting a PR?

scalp42 added a commit to scalp42/consul-cookbook that referenced this issue Dec 3, 2015
@scalp42
retry_interval need to be a string, fixes sous-chefs#244
b65cde2
scalp42 added a commit to scalp42/consul-cookbook that referenced this issue Dec 3, 2015
@scalp42
retry_interval need to be a string, fixes sous-chefs#244
2589d41
@scalp42
Copy link
Contributor

scalp42 commented Dec 3, 2015

@Chili-Man @johnbellone #245

scalp42 added a commit to scalp42/consul-cookbook that referenced this issue Dec 8, 2015
@scalp42
retry_interval need to be a string, fixes sous-chefs#244
39e7db3
johnbellone added a commit that referenced this issue Dec 8, 2015
@johnbellone
Merge pull request #245 from scalp42/patch-2
d86cef5 
retry_interval need to be a string, fixes #244
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@johnbellone @Chili-Man @scalp42