-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provider/aws: Updating CloudFront distribution to correct LoggingConfig #6407
Conversation
return err | ||
} | ||
} else { | ||
err = d.Set("logging_config", []interface{}{}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @jrnt30, I think right here, you'd want to do the following instead:
err = d.Set("logging_config", schema.NewSet(loggingConfigHash, []interface{}{}))
The idea here being that even though it's an empty set you still probably want to pass a *schema.Set
and the correct hash function.
…f disabled - Addresses the issue when local state file has logging_config populated and the user disables the configuration via the UI (or in this case an application of the TF config). This will now properly set the logging_config during the read operation and identify the state as diverging Fixes hashicorp#6390
98bcea6
to
43717e9
Compare
Excellent, thanks! |
…f disabled (hashicorp#6407) - Addresses the issue when local state file has logging_config populated and the user disables the configuration via the UI (or in this case an application of the TF config). This will now properly set the logging_config during the read operation and identify the state as diverging Fixes hashicorp#6390
…f disabled (hashicorp#6407) - Addresses the issue when local state file has logging_config populated and the user disables the configuration via the UI (or in this case an application of the TF config). This will now properly set the logging_config during the read operation and identify the state as diverging Fixes hashicorp#6390
…f disabled (hashicorp#6407) - Addresses the issue when local state file has logging_config populated and the user disables the configuration via the UI (or in this case an application of the TF config). This will now properly set the logging_config during the read operation and identify the state as diverging Fixes hashicorp#6390
…f disabled (hashicorp#6407) - Addresses the issue when local state file has logging_config populated and the user disables the configuration via the UI (or in this case an application of the TF config). This will now properly set the logging_config during the read operation and identify the state as diverging Fixes hashicorp#6390
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. |
disables the configuration via the UI (or in this case an
application of the TF config). This will now properly set the
logging_config during the read operation and identify the state as
diverging
Fixes #6390