-
Notifications
You must be signed in to change notification settings - Fork 258
docs(sem): add secret deletion #4851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| --- | ||
| meta: | ||
| title: How to recover secrets scheduled for deletion | ||
| description: Recover secrets scheduled for deletion in the Scaleway console before they are permanently removed. | ||
| content: | ||
| h1: How to recover secrets scheduled for deletion | ||
| paragraph: Recover secrets scheduled for deletion in the Scaleway console before they are permanently removed. | ||
| tags: secret sensitive-data scheduled-deletion recover-secret | ||
| dates: | ||
| validation: 2025-04-15 | ||
| posted: 2025-04-15 | ||
| categories: | ||
| - identity-and-access-management | ||
| --- | ||
|
|
||
| This page shows you how to recover secrets scheduled for deletion using the Scaleway [console](https://console.scaleway.com). Once you schedule a secret for deletion, it enters a 7-day pending deletion period, during which you can still recover it. | ||
| After this retention period, the secret and all its versions are permanently deleted. | ||
|
|
||
| <Message type="important"> | ||
| Scheduled deletion deletes ephemeral secrets and their versions immediately. | ||
| </Message> | ||
|
|
||
| <Macro id="requirements" /> | ||
|
|
||
| - A Scaleway account logged into the [console](https://console.scaleway.com) | ||
| - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization | ||
| - Created a [secret](/secret-manager/how-to/create-secret/) | ||
| - Scheduled secrets for deletion | ||
|
|
||
| ## How to recover one secret | ||
|
|
||
| 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. | ||
| 2. Select the [region](/secret-manager/concepts/#region) in which to recover the secret, in the **Region** drop-down. | ||
| 3. Click the **Scheduled for deletion** tab. Your secrets display. | ||
| 4. Click <Icon name="more" /> next to the secret you want to recover and click **Recover**. A pop-up displays the estimated cost of recovering the secret. | ||
| <Message type="note"> | ||
| Recovering a secret is billed €0.01 per version associated with the secret. | ||
nerda-codes marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| </Message> | ||
| 5. Click **Recover secret** to confirm. Your secret displays in the **Secrets** tab. | ||
|
|
||
| ## How to recover several secrets | ||
|
|
||
| 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. | ||
| 2. Select the [region](/secret-manager/concepts/#region) in which to recover the secret, in the **Region** drop-down. | ||
| 3. Click the **Scheduled for deletion** tab. Your secrets display. | ||
| 4. Tick the checkbox next to **Name** to select all the secrets you want to recover. | ||
| 5. Click the circular arrow to recover the selected secrets. | ||
| 6. Check the estimated cost and click **Recover secrets** to confirm. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| --- | ||
| meta: | ||
| title: How to recover a version scheduled for deletion | ||
| description: Recover a version scheduled for deletion in the Scaleway console before it is permanently removed. | ||
| content: | ||
| h1: How to recover a version scheduled for deletion | ||
| paragraph: Recover a version scheduled for deletion in the Scaleway console before it is permanently removed. | ||
| tags: secret sensitive-data scheduled-deletion recover-version | ||
| dates: | ||
| validation: 2025-04-15 | ||
| posted: 2025-04-15 | ||
| categories: | ||
| - identity-and-access-management | ||
| --- | ||
|
|
||
| This page shows you how to recover a version scheduled for deletion using the Scaleway [console](https://console.scaleway.com). Once you schedule a version for deletion, it enters a 7-day pending deletion period, during which you can still recover it. | ||
| After this retention period, the version is permanently deleted. | ||
|
|
||
| <Message type="important"> | ||
| Scheduled deletion deletes ephemeral secrets and their versions immediately. | ||
| </Message> | ||
|
|
||
| <Macro id="requirements" /> | ||
|
|
||
| - A Scaleway account logged into the [console](https://console.scaleway.com) | ||
| - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization | ||
| - Created a [version](/secret-manager/how-to/create-version/) | ||
| - Scheduled a version for deletion | ||
|
|
||
| 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. | ||
| 2. Select the [region](/secret-manager/concepts/#region) in which to recover the version, in the **Region** drop-down. | ||
| 3. Access the secret for which you want to recover the version. Your secret's **Overview** tab displays. | ||
| 4. Click the **Versions** tab. | ||
| 5. Click <Icon name="more" /> next to the version you want to recover, and click **Recover**. A pop-up displays the estimated cost of recovering the version. | ||
| <Message type="note"> | ||
| Recovering a version is billed €0.01. | ||
| </Message> | ||
| 6. Click **Recover version** to confirm. You version displays in the **Versions** tab with the same status as before the scheduled deletion. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.