Paul Stack 5ece0f2d04 provider/aws: aws_db_instance restored from snapshot had problem with (#11050) ... subnet_group Fixes #11024 A change was introduced in 0.8.2 that allows db_instances to change their db_subnet_group. Unfortunately, this caused an issue for db_instances that were being restored from snapshot. The restore from snapshot part of create calls the Update func whereas a normal create calls the Read func When calling the Update func, the db_instance was trying to go through a db_subnet_group_name change and was failing for the following reason: ``` InvalidVPCNetworkStateFault: You cannot move DB instance _rds_instance_name_ to subnet group _subnet_group_name_. The specified DB subnet group and DB instance are in the same VPC. Choose a DB subnet group in different VPC than the specified DB instance and try again. ```		2017-01-09 19:10:13 +00:00
..
bins	New provider arukas (#10862)	2017-01-09 17:14:33 +00:00
providers	provider/aws: aws_db_instance restored from snapshot had problem with (#11050)	2017-01-09 19:10:13 +00:00
provisioners	communicator/ssh: don't share rand object to guarantee unique values	2016-12-06 00:21:49 -08:00