Closed bientavu closed 1 year ago
@bientavu you put wrong values on days
and storage_class
. Please change your code from this
{
days = each.value.lifecycle_rules.first_transition_days
storage_class = each.value.lifecycle_rules.second_transition_days
},
{
days = each.value.lifecycle_rules.first_transition_class_type
storage_class = each.value.lifecycle_rules.second_transition_class_type
}
to this
{
days = each.value.lifecycle_rules.first_transition_days
storage_class = each.value.lifecycle_rules.first_transition_class_type
},
{
days = each.value.lifecycle_rules.second_transition_days
storage_class = each.value.lifecycle_rules.second_transition_class_type
}
@abaidgulshan, oh my bad I should have seen that... thanks a lot!
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
Weirdly I have an error saying the type of attribute "days" should be a number. But it is a number in my code... or maybe I'm missing something...
Versions
Module version: v3.14.0
Terraform version: v1.5.7
Provider version(s): v5.17.0
Reproduction Code [Required]
Steps to reproduce the behavior:
main.tf
variables.tf
terraform.tfvars
As you can see my variable is correctly setup with "expiration_days" as a number and I put a number inside my .tfvars. Am I missing something ?
Expected behavior
tf plan goes smoothly and plan a lifecycle policy where my expiration days is correctly setup to 365
Actual behavior
tf plan erorr says "Inappropriate value for attribute "days": a number is required"
Terminal Output Screenshot(s)
Additional context