We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently https://registry.terraform.io/providers/DrFaust92/bitbucket/latest/docs/resources/branch_restriction only supports repo level branch restrictions. However, bitbucket provides a way to do this at the project level: https://support.atlassian.com/bitbucket-cloud/docs/configure-a-projects-branch-restrictions/
I am guessing that might require a new bitbucket_project_branch_restriction resource.
I admit I don't see an obvious way to do this via the API when I look at:
The text was updated successfully, but these errors were encountered:
Im almost certain this is not public API. been looking at this on and off for a while and couldnt make it work via API 🤷
Sorry, something went wrong.
@DrFaust92 - I think you are right. See folks requesting it in https://jira.atlassian.com/browse/BCLOUD-22732. This seems to have led to a way to do it via the UI https://jira.atlassian.com/browse/BCLOUD-14566 but they didn't add to the public API. :-/ It was released fairly recently: https://www.atlassian.com/wac/roadmap/cloud/bitbucket-project-level-branch-restrictions?p=d52b80fb-19
No branches or pull requests
Currently https://registry.terraform.io/providers/DrFaust92/bitbucket/latest/docs/resources/branch_restriction only supports repo level branch restrictions.
However, bitbucket provides a way to do this at the project level: https://support.atlassian.com/bitbucket-cloud/docs/configure-a-projects-branch-restrictions/
I am guessing that might require a new bitbucket_project_branch_restriction resource.
I admit I don't see an obvious way to do this via the API when I look at:
The text was updated successfully, but these errors were encountered: