Imran Nayer

According to `google_sql_database_instance` [documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance) - Second-generation instances include a default 'root'@'%' user with no password. This user will be deleted by Terraform on instance creation. You should use google_sql_user to...

It still applies to provider not this module. Right now provider uses `root_password` paraeter for MsSQL instance only and ignores for MySQL and Postgres. You may wana create issue for...

@mans0954 have you tried this parameter using resource directly? I am not sure if you can set this parameter for cloudSql anymore. Is this a parameter for [legacy HA](https://cloud.google.com/sql/docs/mysql/configure-legacy-ha). I...

Is there an ETA for this release?

in [Change log](https://github.com/terraform-google-modules/terraform-google-vpn/blob/master/CHANGELOG.md) it shows 2.4 after 2.3.1. Strange thing is [Registry](https://registry.terraform.io/modules/terraform-google-modules/vpn/google/4.0.0) is showing 2.3.2 and 2.3.3 release.

@verdel this seems like provider issue. Is it possible if you can recreate this using resource directly and create an issue for the provider team [here](https://github.com/hashicorp/terraform-provider-google/issues).

@verdel yes this is something provider can handle. Just let them know this is a readonly setting and should not be shown as diff. Once you have the issue created...

@verdel do you have an issue open for the provider? If so can u mention it here so we can track it?

@verdel provider should not show the drift on parameters which we dont have any control over. For that reason they need to ignore these changes for diff. They can still...

/gcbrun