feat(imagebuilder-alpha): add support for Image Pipeline Construct

[tarunb12]

Issue

aws/aws-cdk-rfcs#789

Reason for this change

This change adds a new alpha module for EC2 Image Builder L2 Constructs (@aws-cdk/aws-imagebuilder-alpha), as outlined in aws/aws-cdk-rfcs#789. This PR specifically implements the ImagePipeline construct.

Description of changes

This change implements the ImagePipeline construct, which is a higher-level construct of CfnImagePipeline.

Example

const imagePipeline = new imagebuilder.ImagePipeline(this, 'ImagePipeline-AMI', {
  imagePipelineName: 'test-image-pipeline',
  description: 'this is an image pipeline description.',
  recipe: imageRecipe,
  infrastructureConfiguration,
  distributionConfiguration: amiDistributionConfiguration,
  enabled: true,
  executionRole,
  schedule: {
    expression: events.Schedule.expression('cron(0 7 ? * mon *)'),
    timezone: cdk.TimeZone.PST8PDT,
    startCondition: imagebuilder.ScheduleStartCondition.EXPRESSION_MATCH_AND_DEPENDENCY_UPDATES_AVAILABLE,
    autoDisableFailureCount: 5,
  },
  workflows: [{ workflow: imagebuilder.AwsManagedWorkflow.buildImage(this, 'BuildImage') }],
  imageLogGroup,
  imagePipelineLogGroup,
  enhancedImageMetadataEnabled: true,
  imageTestsEnabled: false,
  imageScanningEnabled: false,
});

Describe any new or updated permissions being added

N/A - new L2 construct in alpha module

Description of how you validated changes

Validated with unit tests and integration tests. Manually verified generated CFN templates as well.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

Pull request has been modified.

Pull request has been modified.

Pull request has been modified.

Pull request has been modified.

Pull request has been modified.

[kumsmrit]

Can we extract these conditional permissions to separate helpers? We can follow up with this in separate PR as well

[tarunb12]

Can address in follow up PRs

[aws-cdk-automation]

➡️ PR build request submitted to test-main-pipeline ⬅️

A maintainer must now check the pipeline and add the pr-linter/cli-integ-tested label once the pipeline succeeds.

[mergify]

Merge Queue Status

✅ The pull request has been merged

This pull request spent 31 minutes 7 seconds in the queue, including 30 minutes 58 seconds waiting for CI.
The checks were run in-place.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • feat(imagebuilder-alpha): add support for Image Pipeline Construct #36153
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • feat(imagebuilder-alpha): add support for Image Pipeline Construct #36153
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.