anchor.diff:  
   [source,js]
   -----------------------------------
  -$ curl -XPOST "localhost:9200/_snapshot/my_backup/snapshot_1/_restore" -d '{
  -    "indices": "index_1,index_2",
  -    "ignore_unavailable": "true",
  -    "include_global_state": false,
  -    "rename_pattern": "index_(.+)",
  -    "rename_replacement": "restored_index_$1"
  -}'
  ------------------------------------
  +POST /_snapshot/my_backup/snapshot_1/_restore
  +{
  +  "indices": "index_1,index_2",
  +  "ignore_unavailable": "true",
  +  "include_global_state": false,
  +  "rename_pattern": "index_(.+)",
  +  "rename_replacement": "restored_index_$1"
  +}
  +-----------------------------------
  +// AUTOSENSE
   
   The restore operation can be performed on a functioning cluster. However, an existing index can be only restored if it's
   <<indices-open-close,closed>> and has the same number of shards as the index in the snapshot.
  
positive.code: 
  [source,shell]
  -----------------------------------
  $ curl -XGET "localhost:9200/_snapshot/my_backup/snapshot_1"
  -----------------------------------
  
  All snapshots currently stored in the repository can be listed using the following command:
  
  [source,shell]
  -----------------------------------
  $ curl -XGET "localhost:9200/_snapshot/my_backup/_all"
  -----------------------------------
  
  A snapshot can be deleted from the repository using the following command:
  
  [source,shell]
  -----------------------------------
  $ curl -XDELETE "localhost:9200/_snapshot/my_backup/snapshot_1"
  -----------------------------------
  
  When a snapshot is deleted from a repository, Elasticsearch deletes all files that are associated with the deleted
  snapshot and not used by any other snapshots. If the deleted snapshot operation is executed while the snapshot is being
  
negative.code: 
  [source,shell]
  -----------------------------------
  GET /_snapshot/my_backup/snapshot_1
  -----------------------------------
  // AUTOSENSE
  
  Please note that snapshot info operation uses the same resources and thread pool as the snapshot operation. So,
  executing a snapshot info operation while large shards are being snapshotted can cause the snapshot info operation to wait
  