CLI: support for Stages/nested Cloud Assemblies

Using core Stage, the stage’s stacks are not available when running cdk .

Reproduction Steps

#!/usr/bin/env node
import "source-map-support/register";
import * as cdk from "@aws-cdk/core";

class MyStage extends cdk.Stage {

    constructor(scope: cdk.App, id: string, props: cdk.StageProps) {
        super(scope, id);
        new cdk.Stack(this, "stack");
    }
}

const app = new cdk.App();
new MyStage(app, "stage", {})

Error Log

$ cdk list
This app contains no stacks

Environment

• CLI Version : aws-cli/1.18.77 Python/3.8.3 Linux/5.6.16-300.fc32.x86_64 botocore/1.17.5
• Framework Version: 1.46.0
• Node.js Version: 12.16.1
• OS : Fedora 32
• Language (Version): TypeScript (3.9.3)

Other

I figure the Stage is either broken or supposed to be used in a specific context, but I could not find examples. From the docs it seems to do exactly what I want, that is to group some stacks and instantiate them multiple times with different names/environments. The App is a Stage (which is strange by itself IMHO) but it does not accept an Environment, so one has to do this with a custom construct, ending up with crappy Stack ids… So if it’s not a bug, it’s at least very confusing.

This is 🐛 Bug Report

[tomaszdudek7]

I am quite confused.

CDK Pipelines tutorial https://aws.amazon.com/blogs/developer/cdk-pipelines-continuous-delivery-for-aws-cdk-applications/ uses Stage concept. I followed the tutorial but wanted to deploy the Stage on my own first (before proceeding to CI/CD pipeline creation) - and then I hit this issue.

Do I get it correctly:

• Stages are containers for multiple Stacks (so that for example you have various resources grouped as separate Stacks, Stage is a cointainer for them(that makes a Stage kinda like a topology of your system) and then you create new Stage("qa0"), new Stage("preprod") to have various environments of your system)
• …but they are not ready to use (without CDK Pipelines) yet?

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.