hashicorp / terraform-provider-bitbucket

This Terraform provider is archived per our provider archiving process: https://terraform.io/docs/internals/archiving.html
https://registry.terraform.io
Mozilla Public License 2.0
32 stars 105 forks source link

project_key should not be optional for repos created in a team #10

Open sjauld opened 6 years ago

sjauld commented 6 years ago

Terraform Version

0.10.7

Affected Resource(s)

Terraform Configuration Files

provider bitbucket {
  username = "my_username"
  password = "my_password"
}

resource bitbucket_repository "test" {
  owner = "my_team"
  name  = "test-repo"
}

Debug Output

N/A

Panic Output

N/A

Expected Behavior

------------------------------------------------------------------------

No changes. Infrastructure is up-to-date.

This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed.

Actual Behavior

What actually happened?

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  ~ bitbucket_repository.test
      project_key: "PROJ" => ""

Plan: 0 to add, 1 to change, 0 to destroy.

------------------------------------------------------------------------

Steps to Reproduce

  1. terraform apply
  2. terraform plan

Important Factoids

N/A

References

N/A