Closed nodomain closed 3 years ago
I tried to further analyze the root cause of this by renaming the Kafka resource in the CF template to trigger the creation of a new Kafka cluster:
ClusterName:
Fn::Sub: ${AWS::StackName}-Kafka
Unfortunately this results in the same errors and the CF stack is rolled back.
The result indeed does not contain the requested keys.
The https://github.com/Rungutan/sentry-fargate-cf-stack/releases/tag/1.11.2 release patch should fix this. I think it should work with your existing changed-outside-of-cloudformation Kafka cluster, but not 100% sure about it...
@nodomain
Fixed it by temporarily renaming KafkaGetBrokersLambdaResult
to KafkaGetEndpointsLambdaResult
in the latest version and applying it. This seems to have triggered the needed changes that were prerequisite to a successful upgrade.
After the first run, I re-applied the original CF template in the latest version.
On my staging environment everything went fine yesterday. On my production one it fails with these errors: The only difference besides the instance type is that I manually extended the EBS storage on production already.
Please help - I already found that it seems to have something to do with the result of the lambda because it will output the keys only on "Create" but I am stuck. https://github.com/Rungutan/sentry-fargate-cf-stack/blob/main/cloudformation-template.yaml#L1828
Thanks