7d06ea8449
When computing the set key for an EBS block device, we were using the wrong function; we had hashEphemeralBlockDevice instead of hashEbsBlockDevice. This caused a panic by trying to access the virtual_name attribute that will never be set for EBS block devices. To fix this, I switched to the hashEbsBlockDevice function, which is already being used to compute a Set key in the Schema. But in the default case, where the snapshot_id attribute isn't specified, this also caused a panic. I updated the way the string to hash is generated to check for the existence of the device_name and snapshot_id attributes before we use them, to avoid panics when these optional attributes aren't set. |
||
|---|---|---|
| .. | ||
| bins | ||
| providers | ||
| provisioners | ||