Template format error: YAML not well-formed. (line 120, column 13)

[ghost]

Describe the bug A clear and concise description of what the bug is.

When I update CFCT template using custom-control-tower-initiation.template under aws-control-tower-customizations-2.2.0/deployment, There is template format error: YAML not well-formed. (line 120, column 13)

To Reproduce Steps to reproduce the behavior.

Expected behavior A clear and concise description of what you expected to happen.

Please complete the following information about the solution:

• [v2.2.0] Version: [e.g. v1.0.0]

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0089) - customizations-for-aws-control-tower Solution. Version: v1.0.0". You can also find the version from releases

• [ ] Region: [e.g. us-east-1]
• [ ] Was the solution modified from the version published on this repository?
• [ ] If the answer to the previous question was yes, are the changes available on GitHub?
• [ ] Have you checked your service quotas for the sevices this solution uses?
• [ ] Were there any errors in the CloudWatch Logs?

Screenshots If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context Add any other context about the problem here.

[snebhu3]

Can you retry using https://github.com/aws-solutions/aws-control-tower-customizations/blob/main/customizations-for-aws-control-tower.template

[jo-koe]

Similar error (different line) occurs with latest template:

An error occurred (ValidationError) when calling the ValidateTemplate operation: Template format error: YAML not well-formed. (line 26, column 66)

[balltrev]

Hey @jo-koe can you confirm you're using the latest template published from the v2.3.0 release? We're not able to reproduce the error you're experiencing.

[jo-koe]

Hey @balltrev I was using the latest template, but didn't download it from GitHub in raw format 🤦‍♂️. Works now - Thanks!

[balltrev]

Hey @adenkang feel free to update us with any further information here, in the mean time I'm going to close this issue, thanks!