Closed kartsm closed 1 year ago
This issue has been resolved in version 1.1.1 :tada:
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.
Description
Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration (see the
examples/*
directory for references that you can copy+paste and tailor to match your configs if you are unable to copy your exact configuration). The reproduction MUST be executable by runningterraform init && terraform apply
without any further changes.If your request is for a new feature, please use the
Feature request
template.β οΈ Note
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
Module version [Required]: 1.0.1
Terraform version:
provider registry.terraform.io/hashicorp/aws v4.39.0
Provider version(s): (output identical to above)
Reproduction Code [Required]
Steps to reproduce the behavior:
terraform init
with above codeterraform plan -out apply-${TF_WORKSPACE:-default}.tfplan
terraform apply apply-${TF_WORKSPACE:-default}.tfplan
Expected behavior
Applies successfully.
Actual behavior
The EFS filesystem is created, but the resource is tainted.
If I remove either
transition_to_ia
ortransition_to_primary_storage_class
from mylifecycle_policy
then it will apply just fine. But due to the particularfor_each
expression used bydynamic "lifecycle_policy"
, I don't know if it is possible to construct a data structure that can pass both lifecycle attributes successfully.Terminal Output Screenshot(s)
Additional context
I will be opening a pull request with a suggested fix.