fix(s3deploy): empty sources leads to deployment error

[otaviomacedo]

In the refactor that converted some Lazy calls to the Box API, a case was missed for BucketDeployment: when the sources property is empty. It should generate a custom resource with empty arrays as properties as well. Instead it's generating undefined (resulting in the property not being present in the resource).

Offending source:

this.sources = Box.fromArray(
  props.sources.map((source: ISource) => source.bind(this, { handlerRole: this.handlerRole })),
  { omitEmpty: true },
);

Change it to omitEmpty: false.

Fixes #37784.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[github-actions]

⚠️ This pull request description does not follow the correct template structure.

PRs without a linked issue will receive lower priority for review and merging. Please update the description to follow the PR template and include a line like Closes #123 in the Issue section. If no existing issue matches your change, create one first.

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
This security report is NOT a review blocker. Please try merge from main to avoid findings unrelated to the PR.
To suppress a specific rule, see Suppressing Rules.

---

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results	48 ran	48 passed

Test	Result
No test annotations available

• View Security Guardian Results

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
This security report is NOT a review blocker. Please try merge from main to avoid findings unrelated to the PR.
To suppress a specific rule, see Suppressing Rules.

---

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results with resolved templates	48 ran	48 passed

Test	Result
No test annotations available

• View Security Guardian Results with resolved templates

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-07 09:43 UTC · Rule: default-squash
• ✅ Checks started · in-place
• 🚫 Left the queue — 2026-05-07 10:13 UTC · at 80a2877bb63572a40aba13a0d23c01942ece9756

This pull request spent 29 minutes 51 seconds in the queue, including 29 minutes 29 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • fix(s3deploy): empty sources leads to deployment error #37786
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • fix(s3deploy): empty sources leads to deployment error #37786
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

Reason

Pull request #37786 has been dequeued

The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. Required status check "validate-pr" is queued.

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[kumvprat]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-07 11:16 UTC · Rule: default-squash
• ✅ Checks skipped · PR is already up-to-date
• ✅ Merged — 2026-05-07 11:16 UTC · at 80a2877bb63572a40aba13a0d23c01942ece9756 · squash

This pull request spent 19 seconds in the queue, including 3 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • fix(s3deploy): empty sources leads to deployment error #37786
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • fix(s3deploy): empty sources leads to deployment error #37786
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.