You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
template_properties in the provider can only support key(string):value(string) pairs. The backing API can support key(string):value(any) pairs, like this:
To support arbitrary key:value pairs we need to change template_properties from a Terraform Map to a String of JSON. Similar to how the aws_iam_policy resource does things: reference.
This is a breaking change so we're not going to make it lightly. If you have concerns about this change let us know. If necessary, we will support two workflows for a while with a deprecation period for the old map-based template_properties.
The text was updated successfully, but these errors were encountered:
To elaborate on the "supporting two workflows": We would probably add a new field, maybe called template_props which is the new "String of JSON" field. The old template_properties would then be marked as deprecated and removed in a later release.
Here's some info about how to deprecate attributes in a Terraform provider: reference
template_properties
in the provider can only supportkey(string):value(string)
pairs. The backing API can supportkey(string):value(any)
pairs, like this:To support arbitrary
key:value
pairs we need to changetemplate_properties
from a Terraform Map to a String of JSON. Similar to how theaws_iam_policy
resource does things: reference.This is a breaking change so we're not going to make it lightly. If you have concerns about this change let us know. If necessary, we will support two workflows for a while with a deprecation period for the old map-based
template_properties
.The text was updated successfully, but these errors were encountered: