provider/aws: Allow disabled access_log in ELB #11120
Merged
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.
Fixes #10138
The AWS API does not let you "delete"
access_logs
from an ELB. Currently we simply mark the access logs asdisabled
and move on, however that prevented users from creating and tracking ELBs with disabled access logs... disabledaccess_logs
were not being persisted to state.Here we persist
access_logs
blocks to state if they are found in the configuration, or if they are not in the configuration and the API reports an enabledaccess_logs
configuration.