terraform/configs/configupgrade
Kristin Laemmert 2c78414724
configs/configupgrade: do not panic when int value is out of range (#23394)
`terraform 0.12upgrade` assumes that the configuration has passed 0.11
init, but did not explicitly check that the configuration was valid.
Certain issues would not get caught because the configuration was
syntactically valid. In this case, int or float values out of range
resulted in a panic from `Value()`.

Since running a 0.11 validate command is a breaking change, this PR
merely moves the `Value()` logic for ints and floats into `configupgrade` so
the error can be returned to the user, instead of causing a panic.
2019-11-15 11:02:59 -05:00
..
testdata configs/configupgrade: typo fix (#22469) 2019-08-16 10:38:38 -04:00
analysis.go configupgrade: Improve error message formatting 2019-05-13 13:14:59 +01:00
analysis_expr.go Merge pull request #22846 from hashicorp/jbardin/evaluate-resource 2019-10-08 07:57:15 -04:00
doc.go configupgrade: new package for upgrading configs for 0.12 2018-10-16 18:50:29 -07:00
module_sources.go vendor: switch to HCL 2.0 in the HCL repository 2019-10-02 15:10:21 -07:00
module_sources_test.go vendor: switch to HCL 2.0 in the HCL repository 2019-10-02 15:10:21 -07:00
upgrade.go vendor: switch to HCL 2.0 in the HCL repository 2019-10-02 15:10:21 -07:00
upgrade_body.go vendor: switch to HCL 2.0 in the HCL repository 2019-10-02 15:10:21 -07:00
upgrade_expr.go configs/configupgrade: do not panic when int value is out of range (#23394) 2019-11-15 11:02:59 -05:00
upgrade_native.go vendor: switch to HCL 2.0 in the HCL repository 2019-10-02 15:10:21 -07:00
upgrade_test.go Standardise directory name for test data 2019-06-30 10:16:15 +02:00
upgrader.go terraform: More wiring in of new provider types 2018-10-16 19:12:54 -07:00