# AWS Terraform Upgrade Empty Variables

**URL:** <https://discuss.hashicorp.com/t/aws-terraform-upgrade-empty-variables/36694>\
**Category:** AWS\
**Created:** [March 7, 2022, 4:20pm UTC](https://discuss.hashicorp.com/t/aws-terraform-upgrade-empty-variables/36694 "2022-03-07T16:20:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![erolco](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/erolco/32/26493_2.png) [@erolco](https://discuss.hashicorp.com/u/erolco)\
**Post date:** [March 7, 2022, 4:20pm UTC](https://discuss.hashicorp.com/t/aws-terraform-upgrade-empty-variables/36694/1 "2022-03-07T16:20:32Z")

</div>

Hi everyone,  
Has anyone run into a scenario where, during the terraform version upgrade to 0.15 (from 0.14.11) the tf plan shows in-place changes where it adds empty values like “” for optional attributes. Example is:

this will be updated in-place  
resource “aws\_codebuild\_project” “this” {  
+ badge\_url = “” \<=== like this  
id = “arn:aws:codebuild:XXX”  
name = “name”  
+ source\_version = “” \<=== like this  
# (7 unchanged attributes hidden)  
~ environment {  
+ certificate = “” \<=== like this  
# (5 unchanged attributes hidden)

I don’t think just applying it will have any unintended consequence, but I’d like to hear a second opinion? You can check the \<=== like this above.