Allow for native tagging of resources

[rseuchter-vw]

Feature Description

Make tags a first class citizen of the provider's resources e.g. by adding a tags argument. This could then eventually replace newrelic_entity_tags. Today, tagging resources like newrelic_nrql_alert_condition requires creating a companion resource only for the tags. The companions are prone to errors during maintenance.

Describe Alternatives

There are two obvious alternatives to explicit companion resources:

1. Wrap the original resource type with a module
2. Use for_each to create a) a group of original resources along with b) a corresponding group of newrelic_entity_tags (as is essentially outlined at https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/entity_tags#example-usage)

I don't find any of these alternatives desirable. They both require a lot of boilerplate code for handing all the underlying resource type's arguments down just to get the tags added. I haven't given it much though if the boilerplate code could be easily re-used for different resource types. If not, it would require one of these workarounds for each resource type that needs to be tagged.

Additional context

This is a follow-up to #1420 and is inspired by @rdhar's #1420 (comment).

[NSSPKrishna]

Hi @rseuchter-vw 👋 , thanks for raising the FR. We don't currently have the support from the API to add inline tags for resources that return entity GUID. In order for us to move forward based on the priorities, I have tagged it as an enhancement for the time being.

[rseuchter-vw]

I understand you're situation. As a user / customer it's still sad to hear this and to observe the inconsistency between many resources that require explicit entity tag resources and others like newrelic_synthetics_monitor (and other types of synthetics monitors) that do offer inline tags.

[doteric]

Additionally there should be something like default_tags from the AWS provider that can be used to tag all the resources created by the provider. It would make things a lot cleaner.

[bbraunstein]

+1

We've been expanding my tag footprint to take advantage of the dynamic nature of Workflows. Adding the companion resources makes the TF file more bloated.