wchaws
wchaws
> This is needed for release, or then rewriting the history in main to keep major in v2. But this will leave a version of v3.0.0 in npm.
> I am good with this proposal. Only wondering how this will be have in case the task executes more then one command. Which command will accept the additional args...
echo @matthewfala's analysis, based on my coredump, I can really see the tag length is over 256. Great finding! ``` (gdb) info args in = 0xffffa0a0a280 tag = 0xffff1dcaec80 "loghub.b19bd70c-e6c2-483b-8a9f-b8b2a1bb7c3d.28710911-5270-48e4-9af7-239a082dda71.var.log.containers.saicappsaibotgatewayidentityserver-6596dc44d9-9t99g_default_saicappsaibotgatewayidentityserver-8ac181cc0f5612ec9f3fe3445215a0fdfff5b42eb20826e771ce3e86da44bb2a.log"...
@bogdan-romaniv Hi, can you test out the following template URLs? I think the problem should have been resolved in the [v2.2.0](https://github.com/aws-samples/keycloak-on-aws/releases/tag/v2.2.0) release, which was posted a month ago, but I...
Hi @Hi-Fi, First, thanks for your contribution. But since this PR is blocking the sub-sequential release, I think I have to revert this commit. Besides that, I've been getting security...
Please fix the build error firstly
Root cause: https://github.com/aws/aws-cdk/issues/18090#issuecomment-1853374393
The issue is caused by enabling OpenSearch for a CMK, but the log processor lambda does not have permission to access that CMK. To resolve this, you can manually add...
Hi, @gnom7 can you please provide a sample log? Actually, you could try to manually edit the config generated by `centralized-logging-with-opensearch` and update the parser of the cri `tail` input...