Skip to content

Commit

Permalink
Add the --no-resources option to avoid restoring resources from the …
Browse files Browse the repository at this point in the history
…backup (platformsh#4139)

* Add the --no-resources option to avoid restoring resources from the backup

* Fix oversight
  • Loading branch information
nicogommen authored Aug 6, 2024
1 parent 74f0984 commit 9c3ee95
Showing 1 changed file with 15 additions and 3 deletions.
18 changes: 15 additions & 3 deletions sites/upsun/src/manage-resources/resource-init.md
Original file line number Diff line number Diff line change
Expand Up @@ -356,13 +356,19 @@ you can restore it to your current environment or a different environment.
By default, when you [restore a backup](/environments/restore.md) using the CLI, it is restored to your current environment.
The resources of every container already running on the environment are reverted to their original state when the backup was taken.

{{% note %}}
If you don't want to restore the resources from when the backup was taken,
opt out of restoring the resources.
To do so, when you restore your backup, use the `--no-resources` option.
{{% /note %}}

If you deleted containers after backing up but before restoring, they are recreated using the `backup` strategy.
Meaning, they are granted the same resources as in the backup.

{{% note %}}
If you don't want to restore previously deleted containers,
opt out of restoring the code.
To do so, when you restore your backup, use the `--no-code` flag.
To do so, when you restore your backup, use the `--no-code` option.
{{% /note %}}

When you restore previously deleted containers,
Expand Down Expand Up @@ -398,13 +404,19 @@ title=In the Console
When you [restore a backup](/environments/restore.md) using the Console, it is restored to your current environment.
The resources of every container already running on the environment are reverted to their original state when the backup was taken.

{{% note %}}
If you don't want to restore the resources from when the backup was taken,
opt out of restoring the resources.
To do so, when you restore your backup, use the `--no-resources` option.
{{% /note %}}

If you deleted containers after backing up but before restoring, they are recreated using the `backup` strategy.
Meaning, they are granted the same resources as in the backup.

{{% note %}}
If you don't want to restore previously deleted containers,
opt out of restoring the code.
To do so, restore the backup using the CLI, and use the `--no-code` flag.
To do so, restore the backup using the CLI, and use the `--no-code` option.
{{% /note %}}

{{< /codetabs >}}
Expand Down Expand Up @@ -473,4 +485,4 @@ title=In the Console
4. Select **Sync resources from Production into Staging**.
5. Click **Sync**.

{{< /codetabs >}}
{{< /codetabs >}}

0 comments on commit 9c3ee95

Please sign in to comment.