Open Noel-Jones opened 8 months ago
Further to this, with 3.89 I am seeing that changing the start time does cause the change to be applied
~ schedule {
~ start_time = "2024-01-31T19:10:00Z" -> "2024-01-31T19:10:10Z"
# (5 unchanged attributes hidden)
}
UPDATED COMMENT due to innacuracy!
3.89 works correctly and set the backup time in state file and in the resource.
3.90 does not work. If a new backup time is specified this is not set against the resource and the state file entry is cleared (leading to repeated apply).
3.89 state after apply
"schedule": [
{
"frequency_interval": 1,
"frequency_unit": "Day",
"keep_at_least_one_backup": true,
"last_execution_time": "2024-02-04T19:10:00Z",
"retention_period_days": 60,
"start_time": "2024-01-31T19:10:10Z"
}
3.90 state after apply
"schedule": [
{
"frequency_interval": 1,
"frequency_unit": "Day",
"keep_at_least_one_backup": true,
"last_execution_time": "",
"retention_period_days": 60,
"start_time": ""
}
],
So this is not simply drift. With 3.90 it is not possible to set the start time.
Is there an existing issue for this?
Community Note
Terraform Version
1.6.6
AzureRM Provider Version
3.90.0
Affected Resource(s)/Data Source(s)
azurerm_linux_web_app
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
No change. Your infrastructure matches the configuration.
Actual Behaviour
With v3.90 the start time is always being set
Steps to Reproduce
Upgrade / set provider to 3.90.0 and apply. Change detected. Approve change.
Repeat apply. Change detected. Give up.
Downgrade provider back to 3.89.0 and apply. No change detected.
Important Factoids
No response
References
No response