f993b726b0
enhanced monitoring Fixes #8699 When configuring enhanced monitoring, a user got the following error: ``` * aws_db_instance.db: unexpected state 'configuring-enhanced-monitoring', wanted target '[available]'`` We have added this to the list of pending states we have when creating and updating an RDS instance |
||
---|---|---|
.. | ||
archive | ||
atlas | ||
aws | ||
azure | ||
azurerm | ||
chef | ||
clc | ||
cloudflare | ||
cloudstack | ||
cobbler | ||
consul | ||
datadog | ||
digitalocean | ||
dme | ||
dnsimple | ||
docker | ||
dyn | ||
fastly | ||
github | ||
grafana | ||
heroku | ||
influxdb | ||
librato | ||
logentries | ||
mailgun | ||
mysql | ||
null | ||
openstack | ||
packet | ||
postgresql | ||
powerdns | ||
rabbitmq | ||
random | ||
rundeck | ||
scaleway | ||
softlayer | ||
statuscake | ||
template | ||
terraform | ||
test | ||
tls | ||
triton | ||
ultradns | ||
vcd | ||
vsphere |