There is no response to issues on this repository

[SamStephens]

Tagging @scanlonp because that's the only AWS related account I can see contributing to this repository.

There has been no response to issues I opened against this repository a year ago: #58 and #56. Please prioritise responding to them.

Alternatively, if AWS no longer responds to issues on this repository, turn off Issues in the repository settings so we don't waste our time on issues that will never be actioned.

It's disrespectful of our time and the contribution we're trying to make to the ecosystem when we're allowed to put work into issues that will never be actioned.

[scanlonp]

Hey @SamStephens, completely understand your frustration. This repository is essentially my responsibility to maintain, and it has slipped in my priorities recently. Also, though it does not change that your issues have gone unaddressed, I was not with AWS for a long stretch between this construct's authoring and now.

I have been trying to carve out time to address the issues here, though it will admittedly not be my main focus.

I have seen the issues you have posted; this construct not working for non-TS languages is a massive bug. I know that the issue is a problem with this construct's integration with JSII, but I have not tracked down the fix yet. I can leave comments on each of them and try to get timelines for addressing them. However, it will not be an aggressive schedule.

[SamStephens]

@scanlonp thanks for responding, and thanks for your honesty.

Feel free to resolve this issue.