Fix None injection for hoisted binary arguments

[LeSingh1]

Summary

InjectingArgument.add_to_params in awscli/customizations/binaryhoist.py used pass instead of return in its None guard. When an optional hoisted binary argument is omitted, the method falls through and still injects the wrapped member with a None value.

The sibling class OriginalArgument.add_to_params (same file) correctly returns on None, which confirms the intended behavior.

Impact

This affects the hoisted binary blob arguments:

• aws translate import-terminology (--data-file)
• aws translate translate-document (--document-content)

When the optional argument is omitted, the serialized parameters get polluted, e.g. {'TerminologyData': {'File': None}} instead of staying empty.

Reproduction

from awscli.customizations.binaryhoist import InjectingArgument
arg = InjectingArgument('TerminologyData', 'File', name='data-file', cli_type_name='blob', required=False)
params = {}
arg.add_to_params(params, None)
# before: {'TerminologyData': {'File': None}}
# after:  {}

Fix

     def add_to_params(self, parameters, value):
         if value is None:
-            pass
+            return

Tests

Added tests/unit/customizations/test_binaryhoist.py with three cases (None, wrapping, merge-with-existing). The None case fails before the change and passes after. Verified locally:

$ python -m pytest tests/unit/customizations/test_binaryhoist.py -q
3 passed

---

Developed with AI assistance and verified locally as described above.