You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this is a GitHub PAT, it is required to be manually rotated by creating a new PAT within the GitHub bot account PATs and then copied into the prompt when running Secret Manager locally. However, this means that it's possible for errors to occur if a PAT is rotated and updated in only one of the locations.
Let's determine a path forward for these two secrets.
Suggestions:
Use only one of the PATs. We'd have to determine which will be the only secret to keep and then this will require updating any existing references to the old secret (custom build YAML, variable groups, et cetera, will be impacted).
Rename either or both secrets. Reduces confusion for the next dev manually handling this, however, then we'd still have to update any existing references.
Implement a naming convention for PATs created (in this case, what's created in GitHub) and keep both secrets as is.
Release Note Category
Feature changes/additions
Bug fixes
Internal Infrastructure Improvements
Release Note Description
The text was updated successfully, but these errors were encountered:
The secret called
BotAccount-dotnet-bot-repo-PAT
is used in a few places, one of them being OneLoc builds.Unfortunately, this secret also exists in two different Key Vaults:
maestroprod:
EngKeyVault:
Since this is a GitHub PAT, it is required to be manually rotated by creating a new PAT within the GitHub bot account PATs and then copied into the prompt when running Secret Manager locally. However, this means that it's possible for errors to occur if a PAT is rotated and updated in only one of the locations.
Let's determine a path forward for these two secrets.
Suggestions:
Release Note Category
Release Note Description
The text was updated successfully, but these errors were encountered: