Rico Hermans

> Incomplete CDK Documentation What you're writing about a better tool is correct, but is a big project. There's probably some effective short-term things we can do instead (for example:...

Our default setup does something silly: periodically regenerate all documentation in case the doc generator has changed in the mean time. I would recommend disabling that altogether.

Thanks for the reply Gonzalo. I'm not opposed to VS Code either–what I'm most interested in is simplifying the whole experience and not dumping too much on the participants. Let's...

Can we agree on the following? > It would be good if we were to suggest a *single* development environment, preferably one that does as much as possible to make...

I cannot reproduce this. When I do: ```ts export class TestTokenTagsStack extends cdk.Stack { constructor(scope: cdk.Construct, id: string, props?: cdk.StackProps) { super(scope, id, props); // The code that defines your...

Ohhh! Yes, that actually makes sense. A tag that gets applied to a Stack cannot be a reference to a parameter on that same stack, because they execute in different...

Since you know the build number you need in the build stage, couldn't you just use the build number directly in your CDK app? The generated templates will then contain...

Can you explain how this change breaks you? Only building has been pulled to the front, which shouldn't depend on the bootstrap resources being present. Alternatively, you could start fresh...

Can your custom synthesizer disable version checking on that SSM parameter?

I gotcha. I think the pre-build doesn't need to check the parameter at all, that is just necessary for the publish.