feat: add python option for creating parent packages during copy

[joeyhage]

I added documentation to aws-lambda-builders for its API. I was unable to find the existing BuildProperties documentation to update.

Which issue(s) does this change fix?

#6593

Why is this change necessary?

Python allows ambiguous relative imports so importing uuid is usually from the standard library but could also be a file uuid.py adjacent to the handler module. PEP 8 advises absolute imports or explicit relative imports, and the Google Python Style Guide provides examples of the pitfalls.

How does it address the issue?

This change integrates with a change that was merged in AWS Lambda Builders. It provides a mechanism for explicit package names and auto package names.

What side effects does this change have?

N/A, it is opt-in only.

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• Add input/output type hints to new functions/methods
• Write design document if needed (Do I need to write a design document?)
• Write/update unit tests
• Write/update integration tests
• Write/update functional tests if needed
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

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

[joeyhage]

Note: PR checks will fail until aws-lambda-builders releases 1.58.0 with aws/aws-lambda-builders#765, but everything works locally using pip editable mode and both repos.

[joeyhage]

I noticed that aws-lambda-builders 1.58.0 was released so this is ready for PR workflows now. Thank you!

[reedham-aws]

Yes, we released your builders changes so we could take a look at this one. I will follow up soon. Thanks again for your contributions!

[joeyhage]

I saw some integration tests failed and I have pushed a fix for that issue. I ran the integration tests locally with python 3.12 which is why I didn't see that issue.

For the Update reproducible requirements failure, it looks like a permissions issue since my PR is from a fork.

[joeyhage]

For the Update reproducible requirements failure, it looks like a permissions issue since my PR is from a fork.

I rebased off the develop branch so my PR no longer includes changes to requirements/base.txt and therefore this workflow will not run again.

[reedham-aws]

The code itself looks good to me, nice work @joeyhage!

I don't think there's a place in any of the documentation in this repo that could be updated with this change. Other BuildProperties are documented in official AWS documentation here, so that's something we'd have to take care of internally. I will discuss this internally with the team.

[joeyhage]

Thanks, @reedham-aws! I really appreciate your feedback and support with both PRs for this feature.

[vicheey]

Hi @joeyhage,
Thanks for the great contribution and for being responsive to feedback throughout the review process.
The implementation is clean, well-tested, and properly integrates with existing SAM CLI patterns. I like the dual approach (auto/explicit). Overall look good to me.

[reedham-aws]

After discussing, we will merge this and it will be officially released in the next version of SAM CLI. For the documentation, we will handle it, although it's not blocking for the actual release. Thank you again for your contributions @joeyhage!!

[reedham-aws]

This feature is now documented in https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-build.html

[joeyhage]

Thanks, @reedham-aws! I noticed a typo in the metadata example on that page. The example used snake case and the code is pascal case. Here's the Sam template used in the tests I wrote: https://github.com/aws/aws-sam-cli/blob/develop/tests/integration/testdata/buildcmd/template_with_metadata_python.yaml#L35

[reedham-aws]

I have alerted this issue to the docs team and provided proper snippets with explanations. Thank you for your prompt response @joeyhage!