(amplify): Enable the possibility to configure buildImage
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
Currently in codebuild it's possible to configure in the section _buildSpec_ the object _environment_ and its property _buildImage_.
This property is ignored in an amplify hosting app.
### Use Case
Codebuild, by default, uses a build image version that seems to be old.
Newer versions has many new dependencies installed.
What I'd like to configure is something like this:
```python
new amplify.App(this, 'test', {
sourceCodeProvider: ...,
buildSpec: codebuild.BuildSpec.fromObject({
version: '1.0',
frontend: {
....
buildSpec: codebuild.BuildSpec.fromObject({
version: '1.0',
frontend: {
environment: {
buildImage: LinuxBuildImage.STANDARD_5_0,
privileged: true,
computeType: ComputeType.SMALL,
....
},
```
The `buildImage: LinuxBuildImage.STANDARD_5_0` has some dependecies missing in the current, default, old version, like _jq_ (that seems to be exploited by many users in codebuild).
### Proposed Solution
Please include buildSpec/environment/buildImage or a way to configure the image used by codebuild.
Contributor guide
Research direction
The issue points to Amplify hosting's buildSpec/environment handling and the CodeBuild buildImage setting; begin by locating that integration and its existing configuration coverage. Confirm the change by making buildImage configurable for an Amplify app and verifying that the selected image is passed through to the hosting build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100