can only join an iterable

[Cupidazul]

When VPC tag is only half tagged we get and STNO bug. Expected tags: "Propagate-to"" and "Associate-with". Customers that provided only the "Associate-with" will face issues, since there will be no Approvals records shown in StnoWebApp, but StnoStatus tags say that Approval is required. Workaround: Change tgw tags ApprovalRequired=No to disable Approvals.

Symptom: Approvals stop working.for the VPC.

Erro Log:

CloudWatch > Log groups > STNO-Hub-Failures

https://eu-central-1.console.aws.amazon.com/cloudwatch/home?region=eu-central-1#logsV2:log-groups/log-group/STNO-Hub-Failures/log-events/20c.... "error-info": { "Error": "TypeError", "Cause": "{\"errorMessage\":\"can only join an iterable\",\"errorType\":\"TypeError\",\"requestId\":\"8e3d....d7\",\"stackTrace\":[\" File \\"/var/task/state_machine/index.py\\", line 196, in lambda_handler\n return sns(event, function_name)\n\",\" File \\"/var/task/state_machine/index.py\\", line 147, in sns\n response = sns.notify()\n\",\" File \\"/var/task/state_machine/state_machine_handler.py\\", line 2437, in notify\n self._send_email()\n\",\" File \\"/var/task/state_machine/state_machine_handler.py\\", line 2502, in _send_email\n \\", \\".join(self.event.get(\\"Propagate-to\\")).title(),\n\"]}" }, "Comment": "can only join an iterable"

[gsingh04]

Thank you for raising the issue. The solution requires both Propagate-to and Associate-with tags on the vpc. For better resolution of the issue can you confirm following:

Steps to replicate the issue (please add missing steps):

• Deploy the solution
• Add only Associate-with:<route-table-name> tag on the VPC
• Notice can only join an iterable error in CW log group STNO-Hub-Failures

Expected behavior: Please provide details on the expected behavior after the fix

[Cupidazul]

The tenant was using Terraform and not awscf.

Do note that our symptom was that, after the first half tagging, we entered into a state that, even if we had both tags,.stno web app didnt receive Approvals anymore, but we had many events with both tags.

Sorry to inform, that, as of now, I dont have more info nor am I able to apply a fix.

Just thought I could share this strange behaviour into the project.