We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The changes in PR #1255 appears to have broken my previously working template.
0.21.1 - 0.22.0
1.3.0
{{ $range_min := key "loop_min" | parseInt }}{{ $range_max := key "loop_max" | parseInt | add 1 }}{{ range offset := loop $range_min $range_max }} ...
Pulling an integer value stored in Consul's KV store and sending it through parseInt should provide a value usable by loop.
parseInt
loop
What actually happened?
Upgrading from 0.21.0 to 0.22.0 broke working templates with the following errors:
0.21.0
0.22.0
[ERR] (cli) /etc/rejected.yaml.ctmpl: execute: template: :35:404: executing “” at <loop $range_min $range_max>: error calling loop: loop: bad argument type: int64
{{ $range_min := key "loop_min" | parseInt }}
Are there any other GitHub issues (open or closed) that should be linked here? For example:
The text was updated successfully, but these errors were encountered:
d34ace1
No branches or pull requests
The changes in PR #1255 appears to have broken my previously working template.
Consul Template version
0.21.1 - 0.22.0
Consul Version
1.3.0
Configuration
Expected behavior
Pulling an integer value stored in Consul's KV store and sending it through
parseInt
should provide a value usable byloop
.Actual behavior
What actually happened?
Upgrading from
0.21.0
to0.22.0
broke working templates with the following errors:Steps to reproduce
{{ $range_min := key "loop_min" | parseInt }}
loop
References
Are there any other GitHub issues (open or closed) that should
be linked here? For example:
The text was updated successfully, but these errors were encountered: