Feature request: being able to change behaviour when changing host / username for a mysql_user resource

[ezerfernandes]

Provider version

Terraform v1.6.6
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v5.80.0
+ provider registry.terraform.io/petoju/mysql v3.0.65

MySQL version and settings

mysql  Ver 8.0.40-0ubuntu0.22.04.1 for Linux on x86_64 ((Ubuntu))

Terraform Configuration Files

resource "mysql_user" "svc_user" {
    user = "svc_user"
    host = "%"
}

It was changed to

resource "mysql_user" "svc_user" {
    user = "svc_user"
    host = "10.%"
}

Debug Output

N/A

Panic Output

N/A

Expected Behavior

To have the option of defining that terraform apply on this change would execute

RENAME USER 'svc_user'@'%' TO 'svc_user'@'10.%';

Instead of removing the user and creating a new user. In this way, the password of the MySQL user being used as service user by a production app wouldn't have to be updated and the service wouldn't have to be interrupted.

Actual Behavior

Changing host destroys the DB user and creates a new DB user.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply

Important Factoids

I think the should be an option at the provider level that, by default, keeps the current behaviour, but that can be changed in case that's what's wanted.

References

N/A

[petoju]

Your suggestion makes sense and I don't think there has to be a provider-level setting to preserve the old behavior.
If someone wants to do destroy & create, they can rename the resource.

However, I don't have a lot of time to implement it.