-
Suggestion
-
Resolution: Unresolved
-
None
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
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.