anchor.diff:  
   #### Agent settings
   
  -For the Agent to eventually format, partition and mount attached disk, it needs to somehow identify the disk attachment from inside the OS. The Agent can currently identify attached disk based on either device path, disk's ID, or SCSI volume ID. For example settings below show that CPI attached a disk `vol-7447851` at `/dev/sdd`:
  +For the Agent to eventually format, partition and mount attached disk, it needs to identify the disk attachment from inside the OS. The Agent can currently identify attached disk based on either device path, disk's ID, or SCSI volume ID. For example settings below show that CPI attached a disk `vol-7447851` at `/dev/sdd`:
   
   ```yaml
   {
  
positive.code: ---
  ### <a id="configure-networks"></a> `configure_networks`
  
  Recommened implementation is to raise `Bosh::Clouds::NotSupported` error. This method will be deprecated in API v2.
  
  After the Director received NotSupported error, it will delete the VM (via `delete_vm`) and create a new VM with desired network configuration (via `create_vm`).
  
  
negative.code: 
  Detaches disk from the VM.
  
  If the persistent disk is attached to a VM that will be deleted, it's more likely `delete_vm` CPI method will be called without a call to `detach_disk` with an expectation that `delete_vm` will make sure disks are disassociated from the VM upon its deletion.
  
  Agent settings should have been updated to remove information about given disk.
  
  