-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Switch to official AWS docker images by default #724
Conversation
f880bb8
to
babcb38
Compare
babcb38
to
f89d05d
Compare
Should we also automatically use the matching platform image (e.g. This should be it: const defaultImage = `public.ecr.aws/sam/build-${this.serverless.service.provider.runtime}:latest-${this.serverless.service.provider.architecture}`; Currently to build provider:
name: aws
runtime: python3.9
architecture: arm64
custom:
pythonRequirements:
dockerizePip: true
dockerImage: public.ecr.aws/sam/build-${self:provider.runtime}:latest-${self:provider.architecture} With the suggested change to the PR, the |
Hey @nc-dirknilius, thanks for the proposition. I didn't think of that previously, but it sounds like a really good idea. I'll add that to the PR 👍 |
BREAKING CHANGE: Switches to official AWS docker images from previous `lambci` images that did not support Python 3.9
f89d05d
to
654e0f1
Compare
Overriding the default docker image for serverless is not needed as of serverless/serverless-python-requirements#724
…`6.0.0` With version `6.0.0` of `serverless-python-requirements` they switched to use official AWS docker images. More info can be found in serverless/serverless-python-requirements#724 So we don’t need `lambci/lambda` anymore. With this change everyone who is using `serverless-python-requirements` plugin and will update `serverless-builder`, would have to upgrade `serverless-python-requirements` itself. I was considering two less breaking change approach like: 1. Introduce new plugin class ``` class PythonRequirements600 { } ``` 2. Modification of `PythonRequirements.__init__` and add `version` parameter But to be honest I don’t think it’s worth to maintain this backward compatibility.
…`6.0.0` With version `6.0.0` of `serverless-python-requirements` they switched to use official AWS docker images. More info can be found in serverless/serverless-python-requirements#724 So we don’t need `lambci/lambda` anymore. With this change everyone who is using `serverless-python-requirements` plugin and will update `serverless-builder`, would have to upgrade `serverless-python-requirements` itself. I was considering two less breaking change approach like: 1. Introduce new plugin class ``` class PythonRequirements600 { } ``` 2. Modification of `PythonRequirements.__init__` and add `version` parameter But to be honest I don’t think it’s worth to maintain this backward compatibility.
BREAKING CHANGE: Switches to official AWS docker images from previous
lambci
images that did not support Python 3.9Switch to official images as defaults for packaging with Docker. Please note that it's a breaking change and will be released as a part of next major version of the plugin.
Closes: #647