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

Is there a good way to share a tagging convention across component resources? I use the same AWS tags on resources that are built in the same stack.

My team and I are using this successfully :
<https://www.pulumi.com/blog/automatically-enforcing-aws-resource-tagging-policies/#automatically-applying-tags>
<https://github.com/joeduffy/aws-tags-example/tree/master/autotag-ts>

Hopefully that's what you were looking for

Just note that for overriding the auto injected tags for a particular resource\component, you'll need to 'explode' the default tags from config, with new tags you wanted so in typescript it would be like so:
tags: {...tagsFromConfig, anotherTag:'anotherValue'}

That's exactly what I was looking for. Thanks!

`ResourceTransformationResult` applies to every resource in `is_taggable` so no need to add any additional logic to component resources!
the tags are appended - so you can add custom tags as well

FWIW, this is great, we've merged/updated this code in our `pulumi-components` , but there are some missing / incompatible resources.  Would be amazing if this were maintained.

Here is one issue we've had:
```  // "aws:ecs/service:Service",  // InvalidParameterException: Long arn format must be used for tagging operations```

IIRC something with load balancers was missing tags that was taggable as well