Please consider leaving the privileges v1.0 endpoint available after April 2019

XMLWordPrintable

    • 10

      The team I was hoping to migrate to server before 1.0 is gone is not ready so I need to find a solution to the group endpoint and update my tool to resume this effort for testing late April/May. I don't expect final move till July/Aug.

      Prior to migrating to server, I want to mark each user and group in the repo to read access only. So I need an api for that. I guess I can live without groups and click through each group per repo but how can they not allow PUT api for users??!!

      This call works in the 1.0 API but there is no equivalent in version 2:

      https://confluence.atlassian.com/bitbucket/privileges-endpoint-296093145.html

      PUT https://api.bitbucket.org/1.0/privileges/

      {accountname}

      /

      {repo_slug}

      /

      {privilege_account}

      --data

      {read}

      I have to process over 569 repos and growing so doing by hand is not going to work.

      Is there any way the v1.0 privileges endpoint can be extended similar to what was done for groups or can something be implemented in the 2.0 API to accomplish similar functionality

            Assignee:
            Unassigned
            Reporter:
            Kent Baxley (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: