deploy.py: Handle missing keyholder key with clear error logging (!328) · Merge requests · repos / releng / Scap · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.

How to register an account on GitLab. To prevent spam, new accounts are locked until approved by an admin or the approver bot. You can also file an unlock request to expedite access.

Support: mw:GitLab, how to host a project on GitLab, #wikimedia-gitlab on libera.chat, #GitLab on Phabricator.

Sandeeps requested to merge T313624-improve-keyholder-error-handling into master May 21, 2024

Added logic to abort the deployment process when the keyholder key is not found.
Implemented logging messages to indicate the absence of the keyholder key.
Ensured the process fails gracefully with informative error output to assist in debugging.
User will be prompted for rollback if the key is not found.

Bug: T313624