Skip to content
New issue

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

github_issue_label is not idempotent #13163

Closed
sethvargo opened this issue Mar 29, 2017 · 1 comment · Fixed by #13182
Closed

github_issue_label is not idempotent #13163

sethvargo opened this issue Mar 29, 2017 · 1 comment · Fixed by #13182

Comments

@sethvargo
Copy link
Contributor

Terraform Version

Terraform v0.9.3-dev (51081678a45fdb4276f0a914c848d6a661879ab8+CHANGES)

Affected Resource(s)

  • github_issue_label

Terraform Configuration Files

resource "github_issue_label" "test_repo" {
  repository = "tf-test"
  name       = "enhancement"
  color      = "FF00FF"
}

Error Output

Error applying plan:

1 error(s) occurred:

* github_issue_label.test_repo: 1 error(s) occurred:

* github_issue_label.test_repo: POST https://api.github.com/repos/sethvargo/tf-test/labels: 422 Validation Failed [{Resource:Label Field:name Code:already_exists Message:}]

Expected Behavior

Background: the label "enhancement" already exists. Terraform should have updated the existing "enhancement" label to the new color.

Actual Behavior

Terraform throws an error.

Steps to Reproduce

  1. terraform apply
@ghost
Copy link

ghost commented Apr 14, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants