No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Speaking for <@UB8A66MPS> - I expect this was in pulumi-aws, where he has two open PRs: <https://github.com/pulumi/pulumi-aws/pull/254>.

The failures in CI are fixed with <https://github.com/pulumi/pulumi-aws/pull/256>.

However, CI runs from forks will still not be able to run our full AWS integration tests in our AWS account unfortunately, as doing so would require exposing our AWS account credentials to the forks.  So we'll get some validation, but not all.

Yes, that is what made me ask - I assume with #256 merged, PRs should show up green if they pass the “fast path” tests. I’ll rebase open pull requests onto `master` and push them again when I address the other feedback on them.