provider/aws: Fix crasher in Elastic Beanstalk Configuration with Options #5756
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.
ElasticBeanstalk Configurations will crash if you attempt to use
option_settings
with the following panic:The issue is the
optionSettingHash
method trying to coerce the interface it receives into a* schema.ResourceData
instead of themap[string]interface{}
that it actually is.Another issue that exists is that this resource has it's own implementation of option settings that differs from (but is meant to be identical to) Beanstalk Environments. (ref http://docs.aws.amazon.com/elasticbeanstalk/latest/api/API_CreateEnvironment.html and http://docs.aws.amazon.com/elasticbeanstalk/latest/api/API_CreateConfigurationTemplate.html).
This PR consolidates the implementations into the one used by Environment, and we also change the config option name from
option_settings
to match Beanstalk Environmentssetting
, for consistency. These changes are backwards safe because any use ofoptions_settings
in the Configuration resource is currently crashing anyway.This PR updates the code to be consistent and updates the documentation to match
Fixes #5741