Jon Steinich

Really nice to see this integration. A few initial thoughts: - Would be nice to reference the pre-built provider imports rather than locally generated since using pre-built providers is recommended...

> I vaguely remember that we used to have a bug where storing a reference in a variable and using it in two difference stacks caused cross stack references to...

> in the scenario of running a plan on a stack where it depends on another stack that hasn't yet had the relevant changes applied, is it guaranteed that it...

There is a stack manifest created that includes dependency information. It's possible to write a script that reads it in and then diffs in an appropriate order. Would probably also...

> Ah so we were looking into that but we'd still have to call `cdktf deploy` on (using the previous example again) the `networking` stack before being able to `diff`...

> Is there a way to add a resource to the cross-stack outputs without actually having that resource be used cross-stack yet? Yes, create a `TerraformOutput` containing the data you...

I like this from a versioning perspective, but I worry about it from a security perspective. `.terraform.lock.hcl` functions as both version pinning and checksum matching.

I attempted just doing a graceful shutdown on any startup task failure. This does result in skipping the 10 minute wait cycle, but does not actually resolve the issue. Looking...

> There were quite a few changes between [3.0.2 and 3.6.5](https://github.com/dotnet/orleans/compare/v3.0.2...v3.6.5), one of which may have rectified this issue. Is there something preventing an upgrade? I recommend that before diving...

@ReubenBond I tested this again after upgrading to Orleans 7 and the behavior is the same. I currently have a workaround of wrapping startup tasks and keeping track of failure...