Skip to content

01/29/2025 PM Publishing #291

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.

Sign up for GitHub

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
v-alje merged 1 commit into from
Jan 29, 2025
Merged

01/29/2025 PM Publishing #291

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions reference/ps-modules/Microsoft.PowerShell.SecretManagement/Set-Secret.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
external help file: Microsoft.PowerShell.SecretManagement.dll-Help.xml
Module Name: Microsoft.PowerShell.SecretManagement
ms.date: 10/18/2023
ms.date: 01/29/2025
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.secretmanagement/set-secret?view=ps-modules&wt.mc_id=ps-gethelp
schema: 2.0.0
---
Expand Down Expand Up @@ -291,7 +291,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable

When you run `Set-Secret` with the **Name** parameter to specify the name of the secret, the cmdlet
calls `GetSecret()` that's implemented by the vault extension. `Set-Secret` passes through the name
as provided by the user. The vault extension looks up the secret by that name. If `GetGecret()`
as provided by the user. The vault extension looks up the secret by that name. If `GetSecret()`
returns a match, `Set-Secret` overwrites the secret unless you use the **NoClobber** parameter. The
vault extension always writes the secret information it receives.

Expand Down
Loading