You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changing the elastigroup configuration to e.g. spot_instances: 80 (no ondemand_count) makes "risk": 80 in above JSON, and the terraform plan works perfectly.
As elastigroup.Strategy.Risk is null, value var remains nil and the cast in spotinst.Int(int(*value)) produces the panic. I think this is why changing the elastigroup configuration with a defined value for risk makes it work.
Community Note
Please vote on this issue by adding a 👍 reaction to help the community and maintainers prioritize this request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
The text was updated successfully, but these errors were encountered:
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Debug gist
Panic Output
Panic gist
Expected Behavior
Terraform executes as intended and produces a plan
Actual Behavior
Panic crash
Steps to Reproduce
ondemand_count: 4
terraform plan
Important Factoids
The elastigroup was already created through the GUI with
ondemand_count: 4
, which gives this json as its configuration:Changing the elastigroup configuration to e.g.
spot_instances: 80
(noondemand_count
) makes"risk": 80
in above JSON, and theterraform plan
works perfectly.Hope this is not misleading, but I think the problem is in these lines in fields_spotinst_elastigroup_aws_strategy.go:
As
elastigroup.Strategy.Risk
is null, value var remains nil and the cast inspotinst.Int(int(*value))
produces the panic. I think this is why changing the elastigroup configuration with a defined value for risk makes it work.Community Note
The text was updated successfully, but these errors were encountered: