You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lifecycle policy applied to bucket with transition to glacier after 0 days.
Actual Behavior
Error putting S3 lifecycle: MalformedXML: The XML you provided was not well-formed or did not validate against our published schema
status code: 400, request id: EXAMPLE, host id: EXAMPLE
Steps to Reproduce
terraform apply
Looking at the XML, the required element is missing entirely. As this is an optional parameter (have to specify either days or date) my hunch is that the 0 is evaluating to false so the element isn't being sent. Also tried setting days = "0" as a string with the same result. This may actually be more of a core issue with needing a way to represent a literal 0 that's different from boolean false.
The text was updated successfully, but these errors were encountered:
kjmkznr
added a commit
to kjmkznr/terraform-provider-aws
that referenced
this issue
Jun 23, 2017
Terraform Version
$ terraform -v
Terraform v0.9.8
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/devonbleak/ae05399e61db6c9e94bc2b7eb3a37bce
Expected Behavior
Lifecycle policy applied to bucket with transition to glacier after 0 days.
Actual Behavior
Error putting S3 lifecycle: MalformedXML: The XML you provided was not well-formed or did not validate against our published schema
status code: 400, request id: EXAMPLE, host id: EXAMPLE
Steps to Reproduce
terraform apply
Looking at the XML, the required element is missing entirely. As this is an optional parameter (have to specify either days or date) my hunch is that the 0 is evaluating to false so the element isn't being sent. Also tried setting days = "0" as a string with the same result. This may actually be more of a core issue with needing a way to represent a literal 0 that's different from boolean false.
The text was updated successfully, but these errors were encountered: