GZ
@kaizencc Can I get another review? I would love to have this PR merged.
@kornicameister I would think that as a separate issue and PR. @lpizzinidev I do agree with you that adding a separate props for the removal policy is the best way...
@mergify update
I'll check with Kendra to see if she can provide the detail on her thought soon. If not, I agree with @jochemd that we can merge this PR first to...
@m-radzikowski Thanks for this detailed write up and clear explanation on this issue. There are now 28 people 👍 for this issue and we've escalated it as a `p1` issue....
@m-radzikowski Thanks for sharing your thoughts. I agree that Option 2 seems like the most straightforward and feasible solution among all. In the issue description, you expressed interests to implement...
@MalikAtalla-AWS Any update on this feature? I've a number of reports that customers are stuck due to this conflict.
Hi @deafwolf thanks for creating an issue. Unfortunately, the workaround currently would be manually defining the Lambda Function role and IAM policy with proper permissions you want. We welcome contribution...
For the breaking changes, using `integ.alb.oidc` test as an example, I saw the `template.json` and `assets.json` are modified manually. That could cause breaking changes.
Temporarily adding a `do-not-merge` label to confirm with team that there's no outstanding feedback. Will remove it and merge the PR if none.