Open fgarcia-cnb opened 1 year ago
seems the problem is spark configs use a new method for supplying spak config params. when i let terraform deploy the spark config i see this in Azure:
unfortunately ignoring spark config changes in terraform doesnt resolve the problem. once these settings are set using the correct newer method. the resource becomes unmanagable in terraform
Any updates on this?
I am using azurerm v4.0.3 and still encountering this issue. I also attempted using a json file to match the exact configuration and the plan still fails on the spark config.
Is there an existing issue for this?
Community Note
Terraform Version
1.0.7
AzureRM Provider Version
3.29.1
Affected Resource(s)/Data Source(s)
azurerm_synapse_spark_pool
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
the resource is marked to ignore spark_config parameter, but whenever an unrelated change is made, we get the error above about the sparkconfig not validating. obviously the current spark config is valid since its the current vaue for the resource.
Actual Behaviour
No response
Steps to Reproduce
No response
Important Factoids
JSON snippit of the current value of sparkConfigProperties->content in Azure portal...
References
No response