Masashi Tomooka

I also want this even for Docker Node.js environment to install otel in fewer steps

Hi @TheRealAmazonKendra I really appreciate your review and effort you expended on my PR! So let me summarize the discussion so far. I assume there are currently three possible options...

@TheRealAmazonKendra According to the design guidelines, flat props structure is prefferred over nested structure. ([doc](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md#flat)). I guess it partially explains why most of the log properties are currently designed as...

Hi @TheRealAmazonKendra As I noted on the PR description, I found there will be an issue similar to #16603 in LogRetention construct (i.e. users may remove a log group unintentionally.)...

Hi @stec00 From my perspective there are still two remaining problems for this issue: 1. what API will look like? ([ref](https://github.com/aws/aws-cdk/pull/21820#issuecomment-1234388771)) 2. a log group can be accidentally deleted, as...

@stec00 A workaround would be something like this (not ideal of course): ```ts // In bin/xxxx.ts const app = new cdk.App(); new YourStack(app, "YourStack"); class LogRemover implements IAspect { public...

Hi just to confirm, is it currently possible to access a parent's context from a grandchild route? I mean this kind of situation: ```tsx ``` then can we access the...

Hi @umarjavedse thanks. Yeah I actually tried similar code as above but it did not work. As a workaround I found a way like this (manually inheriting a parent's context...

I found `redshift-alpha` module already supports this feature with custom resources. https://docs.aws.amazon.com/cdk/api/v2/docs/@aws-cdk_aws-redshift-alpha.Table.html maybe we can use a similar way to implement it for the rds module?

At least `"@aws-amplify/ui-react": "^2.19.0"` does not have this problem... Hopefully it will be fixed also in the latest version soon.