Skip to content
This repository has been archived by the owner on Dec 8, 2020. It is now read-only.

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

Open
sjauld opened this issue Oct 4, 2017 · 0 comments
Open

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

sjauld opened this issue Oct 4, 2017 · 0 comments
Labels

Comments

@sjauld
Copy link

sjauld commented Oct 4, 2017

Terraform Version

0.10.7

Affected Resource(s)

  • bitbucket_repository

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

@radeksimko radeksimko added the bug label Oct 9, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants