Audio normalization and remix not computed

[LasseEmilHildebrandt]

Description

The audio normalization and audio remix settings are not actually computed.

These fields have to be actively set, in order to be populated. This causes the 'creation-diff' to be unnecessary confusing.

Relations

Relates #29825
Relates #27824

References

Output from Acceptance Testing

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[github-actions]

Hey @LasseEmilHildebrandt 👋 Thank you very much for your contribution! At times, our maintainers need to make direct edits to pull requests in order to help get it ready to be merged. Your current settings do not allow maintainers to make such edits. To help facilitate this, update your pull request to allow such edits as described in GitHub's Allowing changes to a pull request branch created from a fork documentation. (If you're using a fork owned by an organization, your organization may not allow you to change this setting. If that is the case, let us know.)

[LasseEmilHildebrandt]

Hey @LasseEmilHildebrandt 👋 Thank you very much for your contribution! At times, our maintainers need to make direct edits to pull requests in order to help get it ready to be merged. Your current settings do not allow maintainers to make such edits. To help facilitate this, update your pull request to allow such edits as described in GitHub's Allowing changes to a pull request branch created from a fork documentation. (If you're using a fork owned by an organization, your organization may not allow you to change this setting. If that is the case, let us know.)

We are aware of this issue, and are currently unable to fix this.

[johnsonaj]

@LasseEmilHildebrandt thanks for the contribution! Overall the PR looks good. Before I run test, can you merge/rebase this PR with main? A few dependencies have been added since last week.

[LasseEmilHildebrandt]

Thanks for the review, @johnsonaj - The PR has been rebased unto master.

[johnsonaj]

LGTM 🚀

$ make testacc TESTS=TestAccMediaLiveChannel_ PKG=medialive

==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/medialive/... -v -count 1 -parallel 20 -run='TestAccMediaLiveChannel_'  -timeout 180m
--- PASS: TestAccMediaLiveChannel_disappears (71.42s)
--- PASS: TestAccMediaLiveChannel_hls (87.21s)
--- PASS: TestAccMediaLiveChannel_audioDescriptions_codecSettings (100.72s)
--- PASS: TestAccMediaLiveChannel_basic (150.37s)
--- PASS: TestAccMediaLiveChannel_m2ts_settings (155.12s)
--- PASS: TestAccMediaLiveChannel_update (164.37s)
 --- PASS: TestAccMediaLiveChannel_updateTags (205.26s)
--- PASS: TestAccMediaLiveChannel_UDP_outputSettings (216.16s)
--- PASS: TestAccMediaLiveChannel_status (219.58s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/medialive	222.791s

[johnsonaj]

@LasseEmilHildebrandt thank you for the contribution 🎉

[github-actions]

This functionality has been released in v4.59.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.