AWS cli documentation change
Summary
Added detailed documentation for X12 advanced processing options including split options and validation rules (code list, element length, and element requirement validations)
Security assessment
The changes document new validation capabilities that enhance data integrity and compliance controls, but there's no evidence of addressing a specific security vulnerability. The added validation rules (code list restrictions, length constraints, requirement enforcement) improve security posture by allowing stricter EDI processing controls.
Diff
diff --git a/cli/latest/reference/b2bi/test-conversion.md b/cli/latest/reference/b2bi/test-conversion.md index 9b06c18d4..453400ff7 100644 --- a//cli/latest/reference/b2bi/test-conversion.md +++ b//cli/latest/reference/b2bi/test-conversion.md @@ -15 +15 @@ - * [AWS CLI 2.28.16 Command Reference](../../index.html) » + * [AWS CLI 2.28.19 Command Reference](../../index.html) » @@ -181,6 +181,80 @@ JSON Syntax: - -Shorthand Syntax: - - - fileFormat=string,formatDetails={x12={transactionSet=string,version=string}},outputSampleFile={fileLocation={bucketName=string,key=string}} - +> +> advancedOptions -> (structure) +> +>> A structure that contains advanced options for EDI processing. Currently, only X12 advanced options are supported. +>> +>> x12 -> (structure) +>> +>>> A structure that contains X12-specific advanced options, such as split options for processing X12 EDI files. +>>> +>>> splitOptions -> (structure) +>>> +>>>> Specifies options for splitting X12 EDI files. These options control how large X12 files are divided into smaller, more manageable units. +>>>> +>>>> splitBy -> (string) +>>>> +>>>>> Specifies the method used to split X12 EDI files. Valid values include `TRANSACTION` (split by individual transaction sets), or `NONE` (no splitting). +>>> +>>> validationOptions -> (structure) +>>> +>>>> Specifies validation options for X12 EDI processing. These options control how validation rules are applied during EDI document processing, including custom validation rules for element length constraints, code list validations, and element requirement checks. +>>>> +>>>> validationRules -> (list) +>>>> +>>>>> Specifies a list of validation rules to apply during EDI document processing. These rules can include code list modifications, element length constraints, and element requirement changes. +>>>>> +>>>>> (tagged union structure) +>>>>> +>>>>>> Represents a single validation rule that can be applied during X12 EDI processing. This is a union type that can contain one of several specific validation rule types: code list validation rules for modifying allowed element codes, element length validation rules for enforcing custom length constraints, or element requirement validation rules for changing mandatory/optional status. Each validation rule targets specific aspects of EDI document validation to ensure compliance with trading partner requirements and business rules. +>>>>>> +>>>>>> ### Note +>>>>>> +>>>>>> This is a Tagged Union structure. Only one of the following top level keys can be set: `codeListValidationRule`, `elementLengthValidationRule`, `elementRequirementValidationRule`. +>>>>>> +>>>>>> codeListValidationRule -> (structure) +>>>>>> +>>>>>>> Specifies a code list validation rule that modifies the allowed code values for a specific X12 element. This rule enables you to customize which codes are considered valid for an element, allowing for trading partner-specific code requirements. +>>>>>>> +>>>>>>> elementId -> (string) +>>>>>>> +>>>>>>>> Specifies the four-digit element ID to which the code list modifications apply. This identifies which X12 element will have its allowed code values modified. +>>>>>>> +>>>>>>> codesToAdd -> (list) +>>>>>>> +>>>>>>>> Specifies a list of code values to add to the element’s allowed values. These codes will be considered valid for the specified element in addition to the standard codes defined by the X12 specification. +>>>>>>>> +>>>>>>>> (string) +>>>>>>> +>>>>>>> codesToRemove -> (list) +>>>>>>> +>>>>>>>> Specifies a list of code values to remove from the element’s allowed values. These codes will be considered invalid for the specified element, even if they are part of the standard codes defined by the X12 specification. +>>>>>>>> +>>>>>>>> (string) +>>>>>> +>>>>>> elementLengthValidationRule -> (structure) +>>>>>> +>>>>>>> Specifies an element length validation rule that defines custom length constraints for a specific X12 element. This rule allows you to enforce minimum and maximum length requirements that may differ from the standard X12 specification. +>>>>>>> +>>>>>>> elementId -> (string) +>>>>>>> +>>>>>>>> Specifies the four-digit element ID to which the length constraints will be applied. This identifies which X12 element will have its length requirements modified. +>>>>>>> +>>>>>>> maxLength -> (integer) +>>>>>>> +>>>>>>>> Specifies the maximum allowed length for the identified element. This value must be between 1 and 200 characters and defines the upper limit for the element’s content length. +>>>>>>> +>>>>>>> minLength -> (integer) +>>>>>>> +>>>>>>>> Specifies the minimum required length for the identified element. This value must be between 1 and 200 characters and defines the lower limit for the element’s content length. +>>>>>> +>>>>>> elementRequirementValidationRule -> (structure) +>>>>>> +>>>>>>> Specifies an element requirement validation rule that modifies whether a specific X12 element is required or optional within a segment. This rule provides flexibility to accommodate different trading partner requirements for element presence. +>>>>>>> +>>>>>>> elementPosition -> (string) +>>>>>>> +>>>>>>>> Specifies the position of the element within an X12 segment for which the requirement status will be modified. The format follows the pattern of segment identifier followed by element position (e.g., “ST-01” for the first element of the ST segment). +>>>>>>> +>>>>>>> requirement -> (string) +>>>>>>> +>>>>>>>> Specifies the requirement status for the element at the specified position. Valid values are OPTIONAL (the element may be omitted) or MANDATORY (the element must be present). @@ -203,0 +278,28 @@ JSON Syntax: + }, + "advancedOptions": { + "x12": { + "splitOptions": { + "splitBy": "NONE"|"TRANSACTION" + }, + "validationOptions": { + "validationRules": [ + { + "codeListValidationRule": { + "elementId": "string", + "codesToAdd": ["string", ...], + "codesToRemove": ["string", ...] + }, + "elementLengthValidationRule": { + "elementId": "string", + "maxLength": integer, + "minLength": integer + }, + "elementRequirementValidationRule": { + "elementPosition": "string", + "requirement": "OPTIONAL"|"MANDATORY" + } + } + ... + ] + } + } @@ -313 +415 @@ validationMessages -> (list) -> Returns an array of strings, each containing a message that Amazon Web Services B2B Data Interchange generates during the conversion. +> Returns an array of validation messages that Amazon Web Services B2B Data Interchange generates during the conversion process. These messages include both standard EDI validation results and custom validation messages when custom validation rules are configured. Custom validation messages provide detailed feedback on element length constraints, code list validations, and element requirement checks applied during the outbound EDI generation process. @@ -327 +429 @@ validationMessages -> (list) - * [AWS CLI 2.28.16 Command Reference](../../index.html) » + * [AWS CLI 2.28.19 Command Reference](../../index.html) »