Skip to content

Commit

Permalink
Remove ForceNew from Key project and organization (#10)
Browse files Browse the repository at this point in the history
Without this, the key would always be recreated when using a list
of projects like and adding a new project.

```
resource "sentry_project" "project" {
  count        = "${length(var.apps)}"
  organization = "${sentry_organization.contentful.id}"
  team         = "${sentry_team.default.id}"
  name         = "${element(var.apps, count.index)}"
  resolve_age  = "${var.sentry_resolve_age}"
}

resource "sentry_key" "key" {
  count        = "${length(var.apps)}"
  organization = "${sentry_organization.contentful.id}"
  project      = "${element(sentry_project.project.*.id, count.index)}"
  name         = "Node"
}
```
  • Loading branch information
johanneswuerbach authored and jianyuan committed Jan 22, 2017
1 parent 1539cfb commit d8a3452
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions resource_sentry_key.go
Original file line number Diff line number Diff line change
Expand Up @@ -22,13 +22,11 @@ func resourceSentryKey() *schema.Resource {
"organization": &schema.Schema{
Type: schema.TypeString,
Required: true,
ForceNew: true,
Description: "The slug of the organization the key should be created for",
},
"project": &schema.Schema{
Type: schema.TypeString,
Required: true,
ForceNew: true,
Description: "The slug of the project the key should be created for",
},
"name": &schema.Schema{
Expand Down

0 comments on commit d8a3452

Please sign in to comment.