Skip to content

Commit

Permalink
Update docs
Browse files Browse the repository at this point in the history
  • Loading branch information
craddm committed Dec 7, 2023
1 parent 11d9b25 commit 929eecf
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions docs/source/roles/system_manager/manage_deployments.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,12 +127,12 @@ On your **deployment machine**.
- If you provide the optional `-dryRun` parameter then the names of all affected resources will be printed, but nothing will be deleted
The `SRE_Teardown.ps1` script *does not* remove the SRE data storage account stored in the SHM. Thus, the `ingress`, `egress`, and `backup` data folders still exist.
The `SRE_Teardown.ps1` script *does not* remove the SRE data storage account stored in the SHM. Thus, the `ingress`, `egress`, and `backup` data folders still exist.
This allows the data to be used for the project associated with the SRE to exist before and after the project starts and ends, without requiring the full SRE to be running.
```{attention}
The storage account must be deleted manually through the Azure Portal if desired.
To avoid accidental deletion, the storage account must be deleted manually through the Azure Portal.
The storage account can be found under `RG_SHM_<SHM ID>_PERSISTENT_DATA`, with a name similar to `<SHM ID><SRE ID>data<random letters>`.
Deleting the SRE storage account from `RG_SHM_<SHM ID>_PERSISTENT_DATA` will delete any work that was done in the SRE.
Deleting the SRE storage account from `RG_SHM_<SHM ID>_PERSISTENT_DATA` will delete any work that was done in the SRE.
```

## {{end}} Remove a complete Safe Haven
Expand Down Expand Up @@ -162,12 +162,12 @@ On your **deployment machine**.
If you provide the optional `-dryRun` parameter then the names of all affected resources will be printed, but nothing will be deleted
```
The `SRE_Teardown.ps1` script *does not* remove the SRE data storage account stored in the SHM. Thus, the `ingress`, `egress`, and `backup` data folders still exist.
The `SRE_Teardown.ps1` script *does not* remove the SRE data storage account stored in the SHM. Thus, the `ingress`, `egress`, and `backup` data folders still exist.
This allows the data to be used for the project associated with the SRE to exist before and after the project starts and ends, without requiring the full SRE to be running.
```{attention}
The storage account must be deleted manually through the Azure Portal if desired.
To avoid accidental deletion, the storage account must be deleted manually through the Azure Portal.
The storage account can be found under `RG_SHM_<SHM ID>_PERSISTENT_DATA`, with a name similar to `<SHM ID><SRE ID>data<random letters>`.
Deleting the SRE storage account from `RG_SHM_<SHM ID>_PERSISTENT_DATA` will delete any work that was done in the SRE.
Deleting the SRE storage account from `RG_SHM_<SHM ID>_PERSISTENT_DATA` will delete any work that was done in the SRE.
```

### {{unlock}} Disconnect from the Azure Active Directory
Expand Down

0 comments on commit 929eecf

Please sign in to comment.