feat: document identify_cloud_resources.sh

clouds/g1/brno/security_incidents/README.md

@@ -16,14 +16,15 @@ MetaCentrum Security handles communication with the user - owner of the Openstac
 
 Cloud team transfers the VM snapshot into Openstack project `meta-cloud-metac_sec-cerit_sec`. Access to this project is granted via Perun groups `meta-cloud-admins` (Cloud team) and `meta-sec` (Security team). For the automation checkout [scripts residing in GitLab](https://gitlab.ics.muni.cz/cloud/g2/openstack-infrastructure-as-code-automation/-/tree/master/clouds/g1/brno/security_incidents):
 
-  - `acquire_snapshot_and_create_volume_transfer.sh <THE_ORIGINAL_VM_VOLUME_ID>`
-  - `accept_volume_transfer.sh <VOLUME_TRANSFER_ID>` => results in a new volume with id shared with the Security team. 
+  - `./identify_cloud_resources.sh --fip <public-fip-address>` # reports associated volumes and more info
+  - `./acquire_snapshot_and_create_volume_transfer.sh <THE_ORIGINAL_VM_VOLUME_ID>`
+  - `./accept_volume_transfer.sh <VOLUME_TRANSFER_ID>` => results in a new volume with id shared with the Security team. 
 
 MetaCentrum Security runs a new VM with the new volume attached (not mounted). The VM can be accessed by a private key which is complementary to the provided public key passed in. 
- - `run_vm_with_attached_volume.sh <VOLUME_ID> <SSH_PUB_KEY_LOCATION>`
+ - `./run_vm_with_attached_volume.sh <VOLUME_ID> <SSH_PUB_KEY_LOCATION>`
 
 MetaCentrum Security cleans up the resources
-- `destroy_the_vm.sh`
+- `./destroy_the_vm.sh`
 
 
 #### The provided automation requires following to be in place