Correct true and false OpsWorks string values to fix manage_bundler config bug #7219
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the small change provided by @u2mejc in his comment on issue #5907, in order to fix a bug where the
aws_opsworks_rails_app_layer
resource'smanage_bundler
parameter is ignored, so no matter if you set it totrue
,false
, or don't even set it, the created Rails layer's "Install and manage Bundler" setting is unconditionally "No".There are no existing acceptance tests for
resource_aws_opsworks_rails_app_layer
. Unfortunately, I don't have the time to write them, although it seems like it would be a good opportunity to learn a little Go.But I did compile Terraform in Vagrant (
make dev
) with this change and tested my Terraform template file which setmanage_bundler = true
, and it resulted in the created Rails layer having "Install and manage Bundler" set to "yes". So it does fix that issue, as @u2mejc said.