Snehal Bhurewar

@temporary-github-user unfortunately, we do not have an update on this feature request.

@andy-townsend unfortunately we do not have any update on this feature request.

@steve-g-nz thank you for reaching out. Please may you provide more context on: * What you are trying to do and what is the issue you are facing. * Steps...

Thank you for the additional context. I have created an internal backlog to address this.

@JousP thanks for the feature request. I have created an internal backlog to track this request.

@4claps thanks for reaching out. Please may you provide more details for the error? * CFCT version * Region * Are you seeing this during deployment of CFCT itself? Or...

@pimpuks thank you for reporting the bug and providing the context. I have created an internal backlog to address this edge case and bug.

@awseric thank you for bringing this up. I will create a backlog to look into this.

@willdady Thanks for reaching out, our team is continuing full support for CfCT and have no current plans to change that. The solution goes through the same feature prioritization process...

@awseric we were able to reproduce the issue, and the suggested fix of [pinning PyYAML to 5.3.1 in setup.py](https://github.com/aws-solutions/aws-control-tower-customizations/blob/main/source/src/setup.py#L29) works. We have created an internal backlog to make this change.