SGC-AWS "LargePayload" actions is affected where in the action the default filename is "sg_aws_attachment" (no file extension). - Known Error

SGC-AWS "LargePayload" actions is affected where in the action the default filename is "sg_aws_attachment" (no file extension). Description This error normally occurs when customers have set sn_aws_integ.save_payload_as_attachment property to 'true'. This enables the customer to import large amounts data by saving the output from the flow action in an attachment rather than directly inserting into import set.This error is occurring because the payload is expected to be in certain format and it is not the case when the actual attachment comes in.

This issue occurs only for customers who customize the "glide.attachment.extensions" system property and are on Xanadu. Before Xanadu, there was no limitation on omitting file extensions. Hence, in SG-AWS, file extensions (e.g., .bin, .json) were not explicitly added. However, with Xanadu, the platform team introduced additional validations on "glide.attachment.extensions" system property , leading to this issue.

Steps to Reproduce

1) populate value for glide.attachment.extensions

2)set sn_aws_integ.save_payload_as_attachment property to 'true'

3) test load 20 records for data source "SG-AWS-Software-Inventory"

4) observe the following error: 2024-11-08 10:29:25 (603) worker.0 worker.0 txid=d48a823c83f1 SSI_4e9440ec53903010a3e4ddeeff7b1261 SEVERE *** ERROR *** Encountered error executing instruction: ActionErrorEvalInstruction{id=28, conditions=[], statusKey=rooto.__action_status__, dontTreatAsErrorKey=rooto.__dont_treat_as_error__}, errorMessage:Error encountered while creating Attachment. Attachments of type are not allowed, errorCode:1

Workaround Workaround

This issue is fixed as part of SG-AWS v2.9.Initially we didn't give any default attachment type and the flow action is returning this error due to that. This can be fixed by just adding the attachment type suffix to the filename we are passing to the flow actions and we have updated that tp have .json in the flow actions

SG-AWS-Config-BatchGetResourceConfigLargePayload SG-AWS-Config-BatchGetAggregateResourceConfigLargePayload

Also the customers have to add json in the "glide.attachment.extensions" system property