At present, the provider does not use pagination to retrieve the list of existing SQL users when verifying that a user in the state actually exists. As such, the provider pulls only the first page of SQL users
Subsequently, a cluster with a large number of SQL users will end up with warnings during each Terraform run of This cluster doesn't have a SQL user named... Removing from state.. Attempting to apply will end up with the provider erroring as it attempts to create new users that conflict with existing ones.
At present, the provider does not use pagination to retrieve the list of existing SQL users when verifying that a user in the state actually exists. As such, the provider pulls only the first page of SQL users
Subsequently, a cluster with a large number of SQL users will end up with warnings during each Terraform run of
This cluster doesn't have a SQL user named... Removing from state.. Attempting to apply will end up with the provider erroring as it attempts to create new users that conflict with existing ones.