rehanvdm / cdk-express-pipeline

CDK Express Pipelines is a library built on the AWS CDK, allowing you to define pipelines in a CDK-native method. It leverages the CDK CLI to compute and deploy the correct dependency graph between Waves, Stages, and Stacks using the .addDependency method, making it build-system agnostic and an alternative to AWS CDK Pipelines.
Apache License 2.0
25 stars 1 forks source link

Highlight which Waves, Stages and Stacks will be deployed #5

Open rehanvdm opened 1 month ago

rehanvdm commented 1 month ago

The CDK pattern used for synth/diff/deploy is stored in process.env.CDK_CONTEXT_JSON["aws:cdk:bundling-stacks"] = ["Wave2_*"]. We can use this to highlight what exactly will be deployed.

The current Deployment Order is printed as:

🌊 Wave1
  🔲 Stage1
    📄 StackA (Wave1_Stage1_StackA)
    📄 StackB (Wave1_Stage1_StackB)
        ↳ StackA
🌊 Wave2
  🔲 Stage1
    📄 StackC (Wave2_Stage1_StackC)

I am thinking of highlighting what gets deployed with an > at the beginning of the line, like:

  🌊 Wave1
    🔲 Stage1
      📄 StackA (Wave1_Stage1_StackA)
      📄 StackB (Wave1_Stage1_StackB)
        ↳ StackA
> 🌊 Wave2
>   🔲 Stage1
>     📄 StackC (Wave2_Stage1_StackC)

Make sure the Wves/Stages/Stacks not being deployed line up reasonably well with those that are. The > character might not be the best, it's larger than a space and will only look good on mono fonts. Consider other methods to show this if the > does not work.