Jarrett Spiker

My workaround ended up being ```typescript get friendId() { let inst = this as User; return this.belongsTo("friend").value()?.id; } ``` though I suspect I may be encountering a slightly separate issue

I have confirmed that this still allows for management of data retention policies on TFE v202312-1...the deprecated `DataRetentionPolicy` type will still be populated on read, and update works through the...

Thanks Brandon, definitely agreed that the backward compatibility breaking is the biggest concern here. > We could deprecate the existing method but otherwise leave it unchanged, but this has several...

I am in the process of adding [API documentation](https://github.com/hashicorp/terraform-docs-common/pull/556) for updating data retention policies through the API. Specifically, the documentation includes information on the [different types of data retention policies](https://github.com/hashicorp/terraform-docs-common/pull/556/files#diff-ca75e08d38e893906a50112ac45fc7fbf99357d436e3d619a925e548dacd8bc3R27).

API docs for data retention policies now exist for [workspaces](https://developer.hashicorp.com/terraform/cloud-docs/api-docs/workspaces#show-data-retention-policy), [organizations](https://developer.hashicorp.com/terraform/cloud-docs/api-docs/organizations#show-data-retention-policy), and for the [different types of DRPs](https://developer.hashicorp.com/terraform/enterprise/api-docs/data-retention-policies#data-retention-policy-types). >We could deprecate the existing method but otherwise leave it unchanged, but...

I found a way to maintain backward compatibility on the `Organization` and `Workspace` structs and interfaces. I have maintained the existing `ReadDataRetentionPolicy` function on the interface, which still returns the...