Sync monorepo state at "add input and output constraints to transformers" (#70)

Syncing from
userclouds/userclouds@dc091b8d4723243763779923d0c66b03f70f15a6

Author: uc-build-user

docs/resources/transformer.md

@@ -25,11 +25,65 @@ Manages a Tokenizer transformer. For more details refer to the [transformer docu
 ### Optional
 
 - `description` (String)
+- `input_type_constraints` (Attributes) (see [below for nested schema](#nestedatt--input_type_constraints))
 - `output_type` (String) Valid values: `address`, `birthdate`, `boolean`, `composite`, `date`, `e164_phonenumber`, `email`, `integer`, `phonenumber`, `ssn`, `string`, `timestamp`, `uuid`
+- `output_type_constraints` (Attributes) (see [below for nested schema](#nestedatt--output_type_constraints))
 - `parameters` (String)
 - `reuse_existing_token` (Boolean) Specifies if the tokenizing transformer should return existing token instead of creating a new one.
 - `tag_ids` (List of String)
 
 ### Read-Only
 
 - `id` (String) The ID of this resource.
+
+<a id="nestedatt--input_type_constraints"></a>
+### Nested Schema for `input_type_constraints`
+
+Optional:
+
+- `fields` (Attributes List) The set of fields associated with a column of type composite. Fields cannot be specified if the column type is not composite. (see [below for nested schema](#nestedatt--input_type_constraints--fields))
+- `immutable_required` (Boolean) Can be enabled when unique_id_required is enabled. If true, values for the associated column cannot be modified, but can be added or removed.
+- `unique_id_required` (Boolean) Can be enabled for column type composite or address. If true, each value for the associated column must have a unique string ID, which can either be provided or generated by backend.
+- `unique_required` (Boolean) If true, each value for the associated column must be unique for the user. This is primarily useful for array columns.
+
+<a id="nestedatt--input_type_constraints--fields"></a>
+### Nested Schema for `input_type_constraints.fields`
+
+Required:
+
+- `name` (String) Each part of name must be capitalized or all-caps, separated by underscores. Names may contain alphanumeric characters, and the first part must start with a letter, while other parts may start with a number. (ex. ID_Field_1)
+- `type` (String) Valid values: `address`, `birthdate`, `boolean`, `composite`, `date`, `e164_phonenumber`, `email`, `integer`, `phonenumber`, `ssn`, `string`, `timestamp`, `uuid`
+
+Optional:
+
+- `camel_case_name` (String) Read-only camel-case version of field name, with underscores stripped out. (ex. IDField1)
+- `ignore_for_uniqueness` (Boolean) If true, field value will be ignored when comparing two composite value for a uniqueness check.
+- `required` (Boolean) Whether a value must be specified for the field.
+- `struct_name` (String) Read-only snake-case version of field name, with all letters lowercase. (ex. id_field_1)
+
+
+
+<a id="nestedatt--output_type_constraints"></a>
+### Nested Schema for `output_type_constraints`
+
+Optional:
+
+- `fields` (Attributes List) The set of fields associated with a column of type composite. Fields cannot be specified if the column type is not composite. (see [below for nested schema](#nestedatt--output_type_constraints--fields))
+- `immutable_required` (Boolean) Can be enabled when unique_id_required is enabled. If true, values for the associated column cannot be modified, but can be added or removed.
+- `unique_id_required` (Boolean) Can be enabled for column type composite or address. If true, each value for the associated column must have a unique string ID, which can either be provided or generated by backend.
+- `unique_required` (Boolean) If true, each value for the associated column must be unique for the user. This is primarily useful for array columns.
+
+<a id="nestedatt--output_type_constraints--fields"></a>
+### Nested Schema for `output_type_constraints.fields`
+
+Required:
+
+- `name` (String) Each part of name must be capitalized or all-caps, separated by underscores. Names may contain alphanumeric characters, and the first part must start with a letter, while other parts may start with a number. (ex. ID_Field_1)
+- `type` (String) Valid values: `address`, `birthdate`, `boolean`, `composite`, `date`, `e164_phonenumber`, `email`, `integer`, `phonenumber`, `ssn`, `string`, `timestamp`, `uuid`
+
+Optional:
+
+- `camel_case_name` (String) Read-only camel-case version of field name, with underscores stripped out. (ex. IDField1)
+- `ignore_for_uniqueness` (Boolean) If true, field value will be ignored when comparing two composite value for a uniqueness check.
+- `required` (Boolean) Whether a value must be specified for the field.
+- `struct_name` (String) Read-only snake-case version of field name, with all letters lowercase. (ex. id_field_1)

docs/resources/userstore_column.md

@@ -48,7 +48,7 @@ Optional:
 - `fields` (Attributes List) The set of fields associated with a column of type composite. Fields cannot be specified if the column type is not composite. (see [below for nested schema](#nestedatt--constraints--fields))
 - `immutable_required` (Boolean) Can be enabled when unique_id_required is enabled. If true, values for the associated column cannot be modified, but can be added or removed.
 - `unique_id_required` (Boolean) Can be enabled for column type composite or address. If true, each value for the associated column must have a unique string ID, which can either be provided or generated by backend.
-- `unique_required` (Boolean) If true, each value for the associated column must be unique for the user.
+- `unique_required` (Boolean) If true, each value for the associated column must be unique for the user. This is primarily useful for array columns.
 
 <a id="nestedatt--constraints--fields"></a>
 ### Nested Schema for `constraints.fields`
@@ -60,7 +60,7 @@ Required:
 
 Optional:
 
-- `camel_case_name` (String) Derived camel-case version of field name, with underscores stripped out. (ex. IDField1)
+- `camel_case_name` (String) Read-only camel-case version of field name, with underscores stripped out. (ex. IDField1)
 - `ignore_for_uniqueness` (Boolean) If true, field value will be ignored when comparing two composite value for a uniqueness check.
-- `optional` (Boolean) Whether a value must be specified for the field.
-- `struct_name` (String) Derived snake-case version of field name, with all letters lowercase. (ex. id_field_1)
+- `required` (Boolean) Whether a value must be specified for the field.
+- `struct_name` (String) Read-only snake-case version of field name, with all letters lowercase. (ex. id_field_1)