Better control for public ssh keys at the linked repository configuration

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: Repository (Bitbucket)
    • None
    • 1
    • 1

      Problem definition

      Changing the SSH key requirements from Bitbucket could impact the linked repository from Bamboo side
      As in the below example:

      1. Frokm Bitbucket UI > Administration > Keys and Tokens
      2. Change the RSA key length option
      3. The current SSH key will not be valid as it doesn't meet the key length requirement

      The issue could be resolved by resaving the linked repository configuration to re-generate a new public key to Bitbucket. In case of a large number of linked repositories, this process will be very hard going through every repository and saving the configuration.

      Suggested Solution

      It would be nice if we have an option for bulk saving the configuration or having the linked repositories not impacted by the change of the ssh key length size

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Unassigned
              Reporter:
              Mohamed Ayman (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: