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

I believe the Terraform AWS provider does not yet support this yet - see <https://github.com/terraform-providers/terraform-provider-aws/issues/536>.  Where were you seeing it?

yeah I was looking at that, I saw that #5461 got merged which seems to have an implementation (but was only a quick browse)

further, what would be the recommendation to do this while its unsupported, I couldn’t see any examples of hooking into cloudformation to do something like this: <https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-kinesisanalytics-application.html>

Yes - CloudFormation is a useful escape hatch that is available when something is not yet mapped in Terraform/Pulumi.  See <https://github.com/pulumi/pulumi-aws-infra/blob/master/nodejs/aws-infra/cluster.ts#L315> for an example of using a small snippet of CloudFormation from within a larger Pulumi program.

Note - per <https://github.com/terraform-providers/terraform-provider-aws/issues/536#issuecomment-418506786> it looks like 5461 did not actually add support here.

luke does azure have a similar situation for template with ARM usage?

that might solve my issue with needing the new TF azure provider for a single resource type not yet included

Yes it does - see <https://pulumi.io/reference/pkg/nodejs/@pulumi/azure/core/#TemplateDeployment>.  There are some gotchas due to slightly odd way that ARM template deployments behave around deletion (see note at link above) - but I've worked with several folks who have used this as an escape hatch.

awesome, i'll take a look, ty... i need it for a single role definition so it might work well

aight, yea that works.. the template supports the dataActions params, but since the resources aren't tracked means we'd have to go in and manually remove the role(s) if we update it.. might need one in each region