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
Even if the terraform apply command goes through without printing any error or warning, the checkpoint key doesn't get overridden. Indeed, if trying to run a terraform plan command just afterwards, it requests again to update in place the "Example pipeline" activities JSON to add the portion of code to override the checkpoint key (which should've been already there though): "continuationSettings": { "customizedCheckpointKey": { "value": "@base64(concat('test_region', 'test_model', substring(pipeline().parameters.date, 0, 4), substring(pipeline().parameters.date, 5, 2)))", "type": "Expression" } }
Steps to Reproduce
Run a terraform apply command with the configuration provided above
Check on the ADF portal the activity block called "Sink new telemetry data into a temporary Parquet" to see if the checkpoint key is overridden or not
Run a terraform plan command to see that indeed Terraform detects the portion of JSON code needed to override the key is not present on ADF
Run a terraform apply command again to see nothing changes
After step 1, if you go into the ADF portal and do the trick described in the MS question linked before to let the checkpoint key option show up, the data pipeline works fine but still Terraform is not able to detect the checkpoint key is being overridden and keeps asking me to update in place the state to add the missing code. Also, trying to manually add the missing portion of the JSON on the portal's pipeline editor doesn't work either (the checkpoint key option shows up but then the data pipeline fails as it was not really set).
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
Terraform Version
1.7.4
AzureRM Provider Version
3.94.0
Affected Resource(s)/Data Source(s)
azurerm_data_factory_pipeline
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The "Example pipeline" should run the data flow "exampleSinkDataflow" with an overridden checkpoint key - as recommended by Microsoft in case "you're using a dynamic pattern for your source tables or folders"
Actual Behaviour
Even if the
terraform apply
command goes through without printing any error or warning, the checkpoint key doesn't get overridden. Indeed, if trying to run aterraform plan
command just afterwards, it requests again to update in place the "Example pipeline" activities JSON to add the portion of code to override the checkpoint key (which should've been already there though):"continuationSettings": { "customizedCheckpointKey": { "value": "@base64(concat('test_region', 'test_model', substring(pipeline().parameters.date, 0, 4), substring(pipeline().parameters.date, 5, 2)))", "type": "Expression" } }
Steps to Reproduce
terraform apply
command with the configuration provided aboveterraform plan
command to see that indeed Terraform detects the portion of JSON code needed to override the key is not present on ADFterraform apply
command again to see nothing changesIt's worth to mention that it seems there's an ongoing bug with the ADF portal regarding this specific behaviour. I suppose this might be conflicting with integrations as well like the AzureRM provider, but theoretically it should affect UI only.
After step 1, if you go into the ADF portal and do the trick described in the MS question linked before to let the checkpoint key option show up, the data pipeline works fine but still Terraform is not able to detect the checkpoint key is being overridden and keeps asking me to update in place the state to add the missing code. Also, trying to manually add the missing portion of the JSON on the portal's pipeline editor doesn't work either (the checkpoint key option shows up but then the data pipeline fails as it was not really set).
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: