Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-21703

Include "Branches allowed to deploy" on payload of /2.0/repositories/{workspace}/{repo_slug}/environments/

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently, the response of /2.0/repositories/<workspace>/<repo_slug>/environments/ does not return the corresponding field from the UI named "branches allowed to deploy", which is a list with the only branches that are allowed to deploy to that particular environment.

      This feature request is to include that field in the response of this endpoint.

      Also, allow users to POST/update "branches that are allowed" via API

            [BCLOUD-21703] Include "Branches allowed to deploy" on payload of /2.0/repositories/{workspace}/{repo_slug}/environments/

            We have scripted for automated creation of deployment environments. The only piece that we haven't been able to automate is "Branches allowed to deploy to <env_name>". It is a critical piece because we need to restrict which branches can be used to deploy to specific environments. For example, we do not want to allow a feature branch to be deployed directly to production. Please consider implementing this soon. We need to be able to POST and GET.

            Inapurapu, Aditya added a comment - We have scripted for automated creation of deployment environments. The only piece that we haven't been able to automate is "Branches allowed to deploy to <env_name>". It is a critical piece because we need to restrict which branches can be used to deploy to specific environments. For example, we do not want to allow a feature branch to be deployed directly to production. Please consider implementing this soon. We need to be able to POST and GET.

            We need this to automate the setup of our CD pipelines

            Parth.Joshi added a comment - We need this to automate the setup of our CD pipelines

            Ajay Chandra added a comment - - edited

            Ajay Chandra added a comment - - edited

            We are looking forward to creating our Bitbucket pipeline environments and secrets entirely via the API. 
            Using the GUI for creating and updating is very time consuming and error prone.

            Therefore it is important to us that the API supports all of the current capabilities and security features like the here named deployment restriction for branches. 

            Please add this missing piece in order to complete the environment API.

            Fabian Hoffmann added a comment - We are looking forward to creating our Bitbucket pipeline environments and secrets entirely via the API.  Using the GUI for creating and updating is very time consuming and error prone. Therefore it is important to us that the API supports all of the current capabilities and security features like the here named deployment restriction for branches.  Please add this missing piece in order to complete the environment API.

              Unassigned Unassigned
              lmontiel@atlassian.com Leonardo M
              Votes:
              58 Vote for this issue
              Watchers:
              26 Start watching this issue

                Created:
                Updated: