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

aws_elasticache_parameter_group always dirty #116

Closed
hashibot opened this issue Jun 13, 2017 · 1 comment · Fixed by #1309
Closed

aws_elasticache_parameter_group always dirty #116

hashibot opened this issue Jun 13, 2017 · 1 comment · Fixed by #1309
Labels
bug Addresses a defect in current functionality.

Comments

@hashibot
Copy link

This issue was originally opened by @wr0ngway as hashicorp/terraform#5854. It was migrated here as part of the provider split. The original body of the issue is below.


If I set a single parameter in an aws_elasticache_parameter_group, it does get applied, but subsequently the group is always seen as dirty - i.e. the aws side has multiple params in the group (defaults), but the local side only has the one I set.

resource "aws_elasticache_parameter_group" "cache" {
  name = "cache"
  family = "memcached1.4"
  description = "cache param group"

  parameter {
    name = "max_item_size"
    value = "5242880"
  }
}

result of subsequent plan:

~ aws_elasticache_parameter_group.cache
    parameter.#:                "14" => "1"
    parameter.1156960860.name:  "maxconns_fast" => ""
    parameter.1156960860.value: "0" => ""
    parameter.1159395866.name:  "disable_flush_all" => ""
    parameter.1159395866.value: "0" => ""
    parameter.1390948782.name:  "chunk_size_growth_factor" => ""
    parameter.1390948782.value: "1.25" => ""
    parameter.17563164.name:    "error_on_memory_exhausted" => ""
    parameter.17563164.value:   "0" => ""
    parameter.1849789332.name:  "lru_crawler" => ""
    parameter.1849789332.value: "0" => ""
    parameter.2090287968.name:  "slab_reassign" => ""
    parameter.2090287968.value: "0" => ""
    parameter.2216495271.name:  "expirezero_does_not_evict" => ""
    parameter.2216495271.value: "0" => ""
    parameter.2319007506.name:  "lru_maintainer" => ""
    parameter.2319007506.value: "0" => ""
    parameter.2880467714.name:  "chunk_size" => ""
    parameter.2880467714.value: "48" => ""
    parameter.3394731685.name:  "slab_automove" => ""
    parameter.3394731685.value: "0" => ""
    parameter.3901142929.name:  "cas_disabled" => ""
    parameter.3901142929.value: "0" => ""
    parameter.4132665434.name:  "max_item_size" => "max_item_size"
    parameter.4132665434.value: "5242880" => "5242880"
    parameter.4193572145.name:  "hash_algorithm" => ""
    parameter.4193572145.value: "jenkins" => ""
    parameter.749568046.name:   "memcached_connections_overhead" => ""
    parameter.749568046.value:  "100" => ""
@hashibot hashibot added the bug Addresses a defect in current functionality. label Jun 13, 2017
@ghost
Copy link

ghost commented Apr 11, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant