-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Expected value "1" to be "azurerm_automation_variable_int", actual type is "azurerm_automation_variable_bool" #8953
Comments
…_count both for default as well as other node pools
…_count both for default as well as other node pools
…_count both for default as well as other node pools
…_count both for default as well as other node pools
This functionality has been released in v2.67.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/timbehh/7d07bd9194c083266ffeefa88aa7eefa
Panic Output
Expected Behavior
Automation Account variable of type integer with value 1 is created and terraform apply finishes successfully.
Actual Behavior
When applying for the first time, the variable is created successfully. Immediatly after that the apply fails with the shown error. Subsequent applies fail with the shown error.
The behavior is the same when using the value 0.
The behavior does not occur when using the value 2.
My interpretation:
When getting the variable from azure the values 0 and 1 are interpreted as boolean instead of integer.
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: