Docker-less dependency resolution (CDK \ SAM)

[CoreOxide]

Description

Today, CDK deploy uses docker as it's backend to collect and install dependencies. I'm proposing a way to to that without using Docker. It will also allow building for different OS targets and Lambda runtimes.

There are 2 ways to build without docker:

1. Using native dependency resolution using PIP flags.
2. Using AWS CloudShell (most useful for building Lambda Layers).

As far as I understand, it can be incorporated into PythonFunction or SAM (which also uses Docker under the hood).

Roles

Role	User
Proposed by	@CoreOxide
Author(s)	@alias, @alias, @alias
API Bar Raiser	@alias
Stakeholders	@alias, @alias, @alias

See RFC Process for details

Workflow

• Tracking issue created (label: status/proposed)
• API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
• Kick off meeting
• RFC pull request submitted (label: status/review)
• Community reach out (via Slack and/or Twitter)
• API signed-off (label status/api-approved applied to pull request)
• Final comments period (label: status/final-comments-period)
• Approved and merged (label: status/approved)
• Execution plan submitted (label: status/planning)
• Plan approved and merged (label: status/implementing)
• Implementation complete (label: status/done)

---

Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.

[evgenyka]

Thank you for submitting your RFC! Please be aware that the RFC process is currently on hold, as we announced in August 2023, and we won't be able to review it immediately. We will resume the review of this request once we have clarified the future of the RFC process. I suggest keeping the RFC in status/proposed in the meantime.

[CoreOxide]

Thanks @evgenyka , I will check in periodically.

[mrpackethead]

Will it auto-close for non activity?

[CoreOxide]

Will it auto-close for non activity?

I will try to follow the RFC process renewal and this thread so it won't be lost to time.

[evgenyka]

Not a priority at the moment. Also, this is a feature request in an Experimental (alpha) module. Suggest building your own construct, if you are interested in exploring this concept, and then submit via PR.