Skip to content

PythonFunction additional build options #609

Open
@CoreOxide

Description

@CoreOxide

Description

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

There are 2 ways to build without docker:

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

As @evgenyka suggested in #579, I want to inherit from PythonFunction and intorucde building backend options to the new class.

Looking for your approval before going forward.

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions