Using password for betteruptime_status_page causes Terraform to always set the password even though it has been previously applied and hasn't changed.
Output when terraform plan is run which has password:
Terraform used the selected providers to generate the following
execution plan. Resource actions are indicated with the following
symbols:
~ update in-place
Terraform will perform the following actions:
# betteruptime_status_page.status_page will be updated in-place
~ resource "betteruptime_status_page" "status_page" {
id = "123456"
+ password = "secret-password"
# (10 unchanged attributes hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.
We needed to add a lifecycle rule to avoid this on each run:
Using
password
forbetteruptime_status_page
causes Terraform to always set the password even though it has been previously applied and hasn't changed.Output when
terraform plan
is run which haspassword
:We needed to add a
lifecycle
rule to avoid this on each run:Our resource is created like this: