-
-
Notifications
You must be signed in to change notification settings - Fork 21
Closed
Description
After you create a repository using the bitbucket_repository resource, any changes made to fork_policy do not appear to go through. The original value remains.
Please investigate as to why this is happening, it could be due to the underlying go-bitbucket module not correctly handling this.
Terraform code to reproduce
resource "bitbucket_repository" "za" {
workspace = data.bitbucket_workspace.za.id
name = "abc-def"
project_key = bitbucket_project.za-test.key
fork_policy = "no_public_forks"
}After applying that, change fork_policy
resource "bitbucket_repository" "za" {
workspace = data.bitbucket_workspace.za.id
name = "abc-def"
project_key = bitbucket_project.za-test.key
fork_policy = "no_forks"
}The latter no_forks fork policy will not be made, despite Terraform saying success - this can be verified by re-running the plan which will show the same diff or by going into Bitbucket and viewing the fork policy on the repository.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working