ibm_database CRN backup restore not working

[sflaherty2009]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform IBM Provider Version

terraform v0.15.5

ibm = {
  source = "IBM-Cloud/ibm"
  version = "1.37.1"
}

Affected Resource(s)

• ibm_database

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "ibm_database" "clima_postgres_condition_matching" {
  resource_group_id                    = data.ibm_resource_group.default.id
  name                                 = "${var.base_name}-${var.env_label}-clima-db-postgres-${var.region}-condition-matching"
  service                              = "databases-for-postgresql"
  plan                                 = "standard"
  members_memory_allocation_mb         = 4096
  location                             = var.region
  backup_id                            = var.clima_postgres_condition_matching_backup_crn
  configuration                 = <<CONFIGURATION
    {
      "max_connections": 400, 
      "log_connections": "on",
      "log_disconnections": "on"
    }
    CONFIGURATION
}

Debug Output

 2022/01/11 04:03:23 Terraform apply |       + backup_id                    = "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/4fd48221017bc3ae0817c113177133df:0173b059-ed34-4832-b64e-ca31e07541c9:backup:0173b059-ed34-4832-b64e-ca31e07541c9-inital-backup"
 2022/01/11 04:03:23 Terraform apply |         id                           = "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/4fd48221017bc3ae0817c113177133df:0173b059-ed34-4832-b64e-ca31e07541c9::"
 2022/01/11 04:03:23 Terraform apply |         name                         = "eis-backend-infradev-clima-db-postgres-us-south-ingest-catalog"
 2022/01/11 04:03:23 Terraform apply |         tags                         = [
 2022/01/11 04:03:23 Terraform apply |             "schematics:us-east.workspace.woc_dev_tf_ws.eebbe307",
 2022/01/11 04:03:23 Terraform apply |         ]
 2022/01/11 04:03:23 Terraform apply |         # (25 unchanged attributes hidden)
 2022/01/11 04:03:23 Terraform apply | 
 2022/01/11 04:03:23 Terraform apply |         # (1 unchanged block hidden)
 2022/01/11 04:03:23 Terraform apply |     }
 2022/01/11 04:03:23 Terraform apply | 
 2022/01/11 04:03:23 Terraform apply | Plan: 0 to add, 2 to change, 0 to destroy.
 2022/01/11 04:03:26 Terraform apply | ibm_database.clima_postgres_condition_matching: Modifying... [id=crn:v1:bluemix:public:databases-for-postgresql:us-south:a/4fd48221017bc3ae0817c113177133df:9c7ccbba-493c-43a1-a584-11b86e1c0638::]
 2022/01/11 04:03:26 Terraform apply | ibm_database.clima_postgres_ingest_catalog: Modifying... [id=crn:v1:bluemix:public:databases-for-postgresql:us-south:a/4fd48221017bc3ae0817c113177133df:0173b059-ed34-4832-b64e-ca31e07541c9::]
 2022/01/11 04:03:33 Terraform apply | ibm_database.clima_postgres_condition_matching: Modifications complete after 7s [id=crn:v1:bluemix:public:databases-for-postgresql:us-south:a/4fd48221017bc3ae0817c113177133df:9c7ccbba-493c-43a1-a584-11b86e1c0638::]
 2022/01/11 04:03:33 Terraform apply | ibm_database.clima_postgres_ingest_catalog: Modifications complete after 8s [id=crn:v1:bluemix:public:databases-for-postgresql:us-south:a/4fd48221017bc3ae0817c113177133df:0173b059-ed34-4832-b64e-ca31e07541c9::]```

### Expected Behavior

Database should have been restored with same name and settings as old deployment. 

### Actual Behavior

Terraform Apply ran appropriately and said change was being made but nothing happened

### Steps to Reproduce

<!--- Please list the steps required to reproduce the issue. --->

1. `terraform apply`

### Important Factoids

<!--- Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? --->

### References

<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests

Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor documentation? For example:
--->

* #0000

[sflaherty2009]

Further information related to this ticket...

• What if the DB is lost for some reason? Like it gets accidentally deleted? Or there is a major cloud related outage.
• When you create the new DB from the restore point with a new name and you connect this to the IKS cluster through bindings how do you make modifications to your application config to pull down the new binding? Because at that point the binding name will have changed due to the new naming of the restored cluster. AKA this backup_id setting would need to restore the DB with the same name as the old DB otherwise configuration will need to be changed to use bindings appropriately.