Aaron Friel

I've left a comment here which is applicable to this issue: https://github.com/pulumi/pulumi-cdk/issues/66#issuecomment-1407944836

Hey @sam-goodwin, good to see you kicking the tires on our the CDK interop! It looks like we should change the readme to highlight how to address missing mappings. There...

From a user's point of view, they're using a CDK construct in Pulumi, regardless, `aws` vs `aws-native` is an implementation detail. If we can close the gaps with `aws` we...

I've left a comment here which is applicable to this issue: https://github.com/pulumi/pulumi-cdk/issues/66#issuecomment-1407944836

@wgebis would it be possible to make a release so we can close our own issue here? - https://github.com/pulumi/pulumi-mailgun/issues/119

> We will likely find ourselves holding events in other locations with similar legislation moving forward. This statement is disappointing and sends a strong signal that the CNCF does not...

Current dependencies on/for this PR: * main * **PR #189** 👈 This [stack of pull requests](https://stacking.dev/?utm_source=stack-comment) is managed by [Graphite](https://app.graphite.dev/github/pr/pulumi/esc/189?utm_source=stack-comment).

I would prefer to implement a [previous, current, next] mechanism, to avoid race conditions. > Having three keys allows graceful rotation of the tickets. Services issue tickets with the “current”...

In my experience this sort of thing becomes unwieldy over time. Given the example: ```yaml # Env aws-prod values: aws: login: fn::open::aws-login: # elided ``` ```yaml # Env app values:...

I like that, despite being wordy, as it doesn't close the door on naming contexts later.