app.ts/README.md: add buildImagePipeline as a dependency to every example

without this cdk deploy just one example will not deploy buildImagePipeline

Author: thomas-roos

README.md

@@ -27,15 +27,15 @@ cdk deploy --all
 
 Alternatively to deploy just a specific pipeline example, you can use the CDK deploy command:
 
-EXAMPLE can be one or more of those: QemuEmbeddedLinuxPipeline, PokyAmiPipeline, KasPipeline, RenesasPipeline, NxpImxPipeline
+EXAMPLE can be one or more of those: PokyPipeline, QemuEmbeddedLinuxPipeline, PokyAmiPipeline, KasPipeline, RenesasPipeline, NxpImxPipeline
 
 ```bash
-cdk deploy BuildImagePipeline <EXAMPLE>
+cdk deploy <EXAMPLE>
 ```
 
 The pipelines can be found in the `Developer Tools > Code Pipeline > Pipelines` Console page. The newly created
 pipeline `ubuntu_22_04BuildImagePipeline` should start automatically. If not, it will need to be run before other
-pipelines will work correctly. Once it is complete, the EmbeddedLinuxPipeline in the CodePipeline console page is ready to run. Thus `BuildImagePipeline` must always be part of the deployment if you deploy just a specific example.
+pipelines will work correctly. Once it is complete, the EmbeddedLinuxPipeline in the CodePipeline console page is ready to run. Thus `BuildImagePipeline` will always be a dependency of the deployment if you deploy just a specific example.
 
 ### Removing Pipelines
 The `cdk destroy` command can be used to remove individual pipelines and their related resources. This can also be done in the CloudFormation Console Page.
@@ -55,6 +55,8 @@ The recommended place to view this is from the `Developer Tools > Code Pipeline
 followed by some unique identifier. From the pipeline page, you can find the CodeCommit source repository, the CodeBuild Project (with build logs),
 and the S3 bucket that the image is uploaded to, at the end.
 
+Example stack name: PokyPipeline
+
 #### Using Kas
 The Kas example shows how to use a [Kas Config](https://github.com/aws4embeddedlinux/aws4embeddedlinux-ci/blob/main/source-repo/kas/kas.yml) to manage
 layers. This tool can help programatically manage layers and config with tighter Yocto integration than Git Submodules or the Repo tool.

bin/app.ts

@@ -1,5 +1,6 @@
 #!/usr/bin/env node
 import * as cdk from "aws-cdk-lib";
+import { addDependency } from "aws-cdk-lib/core/lib/deps";
 import {
   EmbeddedLinuxPipelineStack,
   BuildImageDataStack,
@@ -40,7 +41,7 @@ const buildImageRepo = new BuildImageRepoStack(app, "BuildImageRepo", {
   ...defaultProps,
 });
 
-new BuildImagePipelineStack(app, "BuildImagePipeline", {
+const buildImagePipeline = new BuildImagePipelineStack(app, "BuildImagePipeline", {
   ...defaultProps,
   dataBucket: buildImageData.bucket,
   repository: buildImageRepo.repository,
@@ -57,69 +58,75 @@ const vpc = new PipelineNetworkStack(app, {
 /**
  * Create a poky distribution pipeline.
  */
-new EmbeddedLinuxPipelineStack(app, "PokyPipeline", {
+const pokyPipeline = new EmbeddedLinuxPipelineStack(app, "PokyPipeline", {
   ...defaultProps,
   imageRepo: buildImageRepo.repository,
   imageTag: ImageKind.Ubuntu22_04,
   vpc: vpc.vpc,
 });
+pokyPipeline.addDependency(buildImagePipeline)
 
 /**
  * Create a meta-aws-demos pipeline for the Qemu example.
  */
-new EmbeddedLinuxPipelineStack(app, "QemuEmbeddedLinuxPipeline", {
+const qemuEmbeddedLinuxPipeline = new EmbeddedLinuxPipelineStack(app, "QemuEmbeddedLinuxPipeline", {
   ...defaultProps,
   imageRepo: buildImageRepo.repository,
   imageTag: ImageKind.Ubuntu22_04,
   vpc: vpc.vpc,
   layerRepoName: "qemu-demo-layer-repo",
   projectKind: ProjectKind.MetaAwsDemo,
 });
+qemuEmbeddedLinuxPipeline.addDependency(buildImagePipeline)
 
 /**
  * Create an AMI based on Poky.
  */
-new EmbeddedLinuxPipelineStack(app, "PokyAmiPipeline", {
+const pokyAmiPipeline = new EmbeddedLinuxPipelineStack(app, "PokyAmiPipeline", {
   ...defaultProps,
   imageRepo: buildImageRepo.repository,
   imageTag: ImageKind.Ubuntu22_04,
   vpc: vpc.vpc,
   layerRepoName: "ec2-ami-poky-layer-repo",
   projectKind: ProjectKind.PokyAmi,
 });
+pokyAmiPipeline.addDependency(buildImagePipeline)
 
 /**
  * Create an kas based image.
  */
-new EmbeddedLinuxPipelineStack(app, "KasPipeline", {
+const kasPipeline = new EmbeddedLinuxPipelineStack(app, "KasPipeline", {
   ...defaultProps,
   imageRepo: buildImageRepo.repository,
   imageTag: ImageKind.Ubuntu22_04,
   vpc: vpc.vpc,
   layerRepoName: "biga-kas-layer-repo",
   projectKind: ProjectKind.Kas,
 });
+kasPipeline.addDependency(buildImagePipeline)
 
 /**
  * Create an renesas image.
  */
-new EmbeddedLinuxPipelineStack(app, "RenesasPipeline", {
+const renesasPipeline = new EmbeddedLinuxPipelineStack(app, "RenesasPipeline", {
   ...defaultProps,
   imageRepo: buildImageRepo.repository,
   imageTag: ImageKind.Ubuntu22_04,
   vpc: vpc.vpc,
   layerRepoName: "renesas-layer-repo",
   projectKind: ProjectKind.Renesas,
 });
+renesasPipeline.addDependency(buildImagePipeline)
 
 /**
  * Create an nxp image.
  */
-new EmbeddedLinuxPipelineStack(app, "NxpImxPipeline", {
+const nxpImxPipeline = new EmbeddedLinuxPipelineStack(app, "NxpImxPipeline", {
   ...defaultProps,
   imageRepo: buildImageRepo.repository,
   imageTag: ImageKind.Ubuntu22_04,
   vpc: vpc.vpc,
   layerRepoName: "nxp-imx-layer-repo",
   projectKind: ProjectKind.NxpImx,
 });
+nxpImxPipeline.addDependency(buildImagePipeline)