Summary:

Bitbucket offers an expiry option for Access keys on repositories to set SSH keys to expire after a specified number of days. https://confluence.atlassian.com/bitbucketserver/ssh-access-keys-for-system-use-776639781.html

When the expiration is set for SSH keys on Bitbucket DC, repositories will stop functioning once the keys expire, as they will no longer be valid.

Suggestion

We want to have a feature in Bamboo that automatically renews all the SSH keys on expiration without breaking repository access or impacting customer business, which relies on a huge number of BB-linked repos.

We have a REST API endpoint to regenerate SSH keys in Bamboo, but we can only do this after the keys expire.

Even this will cause performance issues when there are huge numbers of linked repo lists to get re-generated.