Update module github.com/upbound/provider-aws to v0.47.4

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/upbound/provider-aws	v0.47.1 -> v0.47.4

---

Release Notes

upbound/provider-aws (github.com/upbound/provider-aws)

v0.47.4

Compare Source

The release 0.47.4 sets a default io.Discard logger for the controller-runtime if debug logging is not enabled which fixes https://github.com/crossplane-contrib/provider-upjet-aws/issues/974 and https://github.com/crossplane-contrib/provider-upjet-aws/issues/854. If debug logging is enabled, then the controller-runtime uses a debug mode zap logger as usual.

What's Changed

• Set log.Default's output to io.Discard by @​ulucinar in https://github.com/crossplane-contrib/provider-upjet-aws/pull/1215

Full Changelog: https://github.com/crossplane-contrib/provider-upjet-aws/compare/v0.47.3...v0.47.4

v0.47.3

Compare Source

The release v0.47.3 includes two important bug fixes detailed below:

• The first fix is related to sensitive fieldpath generation for slice-type fields. In the current behavior, we do not have any handling mechanism for slices while calculating the fieldpath for sensitive fields. With this PR we will have this and correctly generate the fieldpaths for sensitive slice typed fields. We started to generate the correct fieldpath for the passwordsSecretRef field of the elasticache.User resource. In this way, we will correctly resolve the sensitive data for this field. Related upstream fix: https://github.com/crossplane/upjet/pull/355
• The second fix removes the applying of StateFuncs to parameters in the upstream with this PR. We noticed that the user_data field of the ec2.Instance resource does not work properly. Please see this issue. The related field started working correctly with the fix of a bug we found in Upjet.

What's Changed

• Reclaim disk space in an initial step while running the CI jobs by @​ulucinar in https://github.com/upbound/provider-aws/pull/1197
• [release-0.47] Bump upjet to 1.1.3 by @​sergenyalcin in https://github.com/upbound/provider-aws/pull/1195

Full Changelog: https://github.com/upbound/provider-aws/compare/v0.47.2...v0.47.3

v0.47.2

Compare Source

The release v0.47.2 includes some important bug fixes & dependency bumps detailed below:

• Bump upjet to v1.1.1
• Bump crossplane-runtime to commit 7fcb8c5cad6f
• Bump uptest to v0.11.0
• Fixes an update loop issue for the Firewall.networkfirewall resource https://github.com/upbound/provider-aws/pull/1160
• AWS Secrets Manager Provider Constantly Adds and Deletes Regional Replication https://github.com/upbound/provider-aws/issues/1079
• [Bug]: Secret never Synchttps://github.com/upbound/provider-aws/issues/11288
• v0.46.0 broke localstack config https://github.com/upbound/provider-aws/issues/1063

What's Changed

• [Backport release-0.47] fix Secret/secretmanagers.aws update loop for replica field and custom diff logic when replica config is empty by @​turkenf in https://github.com/upbound/provider-aws/pull/1158
• [Backport release-0.47] Make endpoint provider configuration value single-element list by @​turkenf in https://github.com/upbound/provider-aws/pull/1156
• Bump upjet to v1.1.1 by @​ulucinar in https://github.com/upbound/provider-aws/pull/1160
• [Backport release-0.47] tests and testing changes by @​mbbush in https://github.com/upbound/provider-aws/pull/1161

Full Changelog: https://github.com/upbound/provider-aws/compare/v0.47.1...v0.47.2

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.