docs(best-practices): all resource attributes (#750)

Co-authored-by: Erik Osterman (CEO @ Cloud Posse) <[email protected]>
Co-authored-by: Dan Miller <[email protected]>

Author: 3 people

docs/best-practices/terraform.mdx

@@ -273,6 +273,28 @@ We prefer to keep terraform outputs symmetrical as much as possible with the ups
 
 ![Terraform outputs should be symmetrical](/assets/terraform-outputs-should-be-symmetrical.png)
 
+### Export all Attributes of a Resource
+
+While it's important to explicitly output the most relevant attributes from a resource, there are cases where exposing the entire resource object is beneficial. By outputting the full resource, you provide downstream modules and users with greater flexibility and easier interoperability—especially when composing infrastructure across multiple modules.
+
+This approach also future-proofs your module. As providers evolve and introduce new attributes, consumers can immediately access those attributes without requiring the module to be updated with new outputs.
+
+```hcl
+output "<resource_type>_<resource_name>" {
+  value       = <resource_type>.<resource_name>
+  description = "All attributes of [`<resource_type>.<resource_name>`](link-to-aws-provider-resource-attribute-docs)"
+}
+```
+
+For example, if the module contained the resource address `aws_ec2_instance.default` then the output would be defined like this.
+
+```hcl
+output "aws_ec2_instance_default" {
+  value       = aws_ec2_instance.default
+  description = "All attributes of [`aws_ec2_instance.default`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance#attribute-reference)"
+}
+```
+
 ## Language
 
 ### Use indented `HEREDOC` syntax