provider/aws : Opsworks fails on update

[u2mejc]

Opsworks fails during updates:

Error applying plan:

1 error(s) occurred:

* aws_opsworks_stack.main: ValidationException: Custom Cookbooks Source's Type: Unsupported scm type
        status code: 400, request id: *snip*

This is due to the provider "computing" empty fields and adding it to the JSON request:

2016/04/07 19:17:06 [DEBUG] terraform-provider-aws:   CustomCookbooksSource: {
2016/04/07 19:17:06 [DEBUG] terraform-provider-aws:     Password: "",
2016/04/07 19:17:06 [DEBUG] terraform-provider-aws:     Revision: "",
2016/04/07 19:17:06 [DEBUG] terraform-provider-aws:     SshKey: "",
2016/04/07 19:17:06 [DEBUG] terraform-provider-aws:     Type: "",
2016/04/07 19:17:06 [DEBUG] terraform-provider-aws:     Url: "",
2016/04/07 19:17:06 [DEBUG] terraform-provider-aws:     Username: ""
2016/04/07 19:17:06 [DEBUG] terraform-provider-aws:   },

[catsby]

Hey @u2mejc – do you have a simple config that demonstrates this problem? The computed flag tells Terraform that the API may return data and to not worry about it; the resource itself is not populating empty data on it's own. Or, it shouldn't 😄

I did some debugging, and found that the CustomCookbooksSource source that's returned from DescribeStacks call here is coming back empty, instead of the typical nil. As a result we're storing empty values when we should omit it if nothing there is found. Do you think you could adjust #6078 to account for that?

[u2mejc]

Please see comments in PR: #6078

[ghost]

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.