Add support for deploy keys in API v2

Issue #17069 resolved
Kraig
created an issue

API support of deployment keys in V2 is critical for our CI and without that support is will cause us to move away from BitBucket.

This feature has been in place in v1 and now removing it as of 12/31/2018 is a very big deal for those of use who use these extensively.

Please, add the feature back or provide guide on what the proposed work-a-round would be.

Thank you.

Official response

  • Jarred Colli staff

    Hi Everyone,

    After getting some feedback about the importance of Deploy Keys, we're working to build support for them in our v2 APIs. We will have that launched well ahead of our deprecation date for the v1 apis, to ensure that everyone has time to adjust their integrations accordingly.

    Jarred from the Bitbucket Team

Comments (25)

  1. Nikos Mavrakis

    +1 for this feature request.
    I used to use this feature to clone my project from BitBucket to my server automatically (via Ansible). Now I have to do it manually each time which is annoying.
    Please add this feature.
    Thank you :)

  2. Ragesh Krishna

    Managing deploy keys via the API is critical for any CI/CD service to integrate with BitBucket. What is the rationale for not providing an API to do this? How do you suggest CI/CD providers integrate with BitBucket once the v1 API is removed?

  3. Ben Chavet

    CI/CD providers will have to resort to user-level keys. This opens security concerns, where a user that has access to the CI/CD system now potentially has access to every repo that the user who set up the CI/CD system has access to, even if they shouldn't. With deploy keys, this access is limited to the single repository.

    Removing this feature from the API is a huge step backwards, and I can't see any good reason for it.

  4. James Jones

    +1 A few months ago I moved my repos from AWS Codecommit to Bitbucket. If deploy keys API is being removed then I'll need to go back to AWS. Why on earth are you removing this feature from the API?

  5. Anthony

    Another CI provider here. We rely on this API for our service. What is the recommendation for users requiring the API v1 endpoint, move to user keys or have users manually set up SSH keys? Without this endpoint, we'll likely drop support for Bitbucket entirely.

  6. Bernd Konrad

    Having this feature is a must for us too. If it isn't added soon, like OP, we'll be forced to switch git providers.

    In general, I'd really like to hear an explanation as to why atlassian thinks it's ok to take away API functionality at all. You just don't do that. That's API Design 101.

  7. Mark Smith

    This feature is a must for me too, I have some provisioning workflows that depend on it, having to manually add the keys to the repo would be a big set back.

  8. Ragesh Krishna

    Can someone from Atlassian please provide some kind of an update on this? We're 6 weeks away from when this is going to start breaking stuff. It would be nice if we could get an official response so we can make concrete plans to deal with this.

  9. Jon Baker

    I am pretty sure I saw something this summer that Atlassian is officially dropping the API access to deploy keys intentionally in another ticket here (too busy to look it up right now). So unless this thread can change their mind, I would start planning accordingly assuming they are not going to add it to v2.

  10. Jon Baker

    Well, after I posted that my curiosity got the best of me. Here is their official position: https://developer.atlassian.com/cloud/bitbucket/deprecation-notice-v1-apis/?_ga=2.47157793.769876782.1542379763-1399483184.1455836711#deploykeys

    "Deploy keys are a special kind of account-level SSH key that provide read-only access to a repository for running CI and deployments. We aren’t exposing deploy keys in the 2.0 API. Deploy keys can no longer be managed using the REST API."

  11. Bernd Konrad

    Thanks Jon for looking that up. In typical Atlassian fashion, the post fails to mention any kind of reasoning for this decision, yet they explain to us what deploy keys are, in case we used them yet didn't know what they where. Thanks Atlassian :)

    Meh, we'll start migrating to the competition, i guess...

  12. Jarred Colli staff

    Hi Everyone,

    After getting some feedback about the importance of Deploy Keys, we're working to build support for them in our v2 APIs. We will have that launched well ahead of our deprecation date for the v1 apis, to ensure that everyone has time to adjust their integrations accordingly.

    Jarred from the Bitbucket Team

  13. Log in to comment