search

Rungutan / sentry-fargate-cf-stack

AWS CloudFormation template to launch a highly-available Sentry 20 stack through ECS Fargate at the minimum cost possible
Apache License 2.0
60 stars 16 forks source link

The EMAIL_USE_SSL setting is deprecated. Please use SENTRY_OPTIONS['mail.use-ssl'] instead. #2

Closed nodomain closed 3 years ago

nodomain commented 3 years ago

This came to my attention when looking at the Warnings in the admin menu.

The EMAIL_USE_SSL setting is deprecated. Please use SENTRY_OPTIONS['mail.use-ssl'] instead.

nodomain commented 3 years ago

Seems to be similar to https://github.com/getsentry/onpremise/issues/718 image

mariusmitrofan commented 3 years ago

The warning in the top bar no longer appears, but you'll still see it in the logs due to a bug in Sentry unfortunately

nodomain commented 3 years ago

Awesome.

Any idea how to mitigate this?

ClickHouseBoostrapLambdaResultSingleExecution | UPDATE_FAILED | Failed to update resource. See the details in CloudWatch Log Stream: 2021/01/21/[$LATEST]9cbac80fd00446909ac0fb22631c02f4 | Custom::ClickHouseBootstrapSingleExecution | 2021/01/21/[$LATEST]9cbac80fd00446909ac0fb22631c02f4

Afterwards it rolls back. I uploaded the new CloudFormation file and updated the parameters accordingly (1.2.1 instead of latest).

nodomain commented 3 years ago

Note: I am unable to find the referenced logstream.

mariusmitrofan commented 3 years ago

I remember already testing update from 1.0.0 and 1.1.0 to latest and didn't have any problems.

To find the log stream you have to search the log group by the stack name and then it should be there.

Aka if my stack would be "sentry-rungutan-test" then this link would show me directly those correct log groups ->

https://console.aws.amazon.com/cloudwatch/home#logsV2:log-groups$3FlogGroupNameFilter$3Dsentry-rungutan-test

PS: Make sure you're in the proper region

mariusmitrofan commented 3 years ago

btw @nodomain -> if you don't have any data in it, just delete the stack and create a new one :)

nodomain commented 3 years ago

Found it. Mixed up the time zones.

{
    "Status": "FAILED",
    "Reason": "See the details in CloudWatch Log Stream: 2021/01/21/[$LATEST]9cbac80fd00446909ac0fb22631c02f4",
    "PhysicalResourceId": "2021/01/21/[$LATEST]9cbac80fd00446909ac0fb22631c02f4",
    "StackId": "arn:aws:cloudformation:eu-central-1:722716701248:stack/Sentry/387ae980-5b2c-11eb-9af6-0a306114f79c",
    "RequestId": "4c27cbb5-a079-48d4-ac8c-832845186ddc",
    "LogicalResourceId": "ClickHouseBoostrapLambdaResultSingleExecution",
    "NoEcho": false,
    "Data": {
        "Reason": "string indices must be integers"
    }
}
nodomain commented 3 years ago

Unfortunately we are using it already :)

mariusmitrofan commented 3 years ago

Unfortunately

So is it working now...?

nodomain commented 3 years ago

I’ll have a debugging session tonight and give you feedback. Trying to understand the various components at the moment.

mariusmitrofan commented 3 years ago

Let's do it together then.

Use calendly.com/marius-mitrofan to schedule a Zoom call!

nodomain commented 3 years ago

Thanks! Sent an invite.

nodomain commented 3 years ago

I think we can skip the Zoom call. I found it and proposed a fix. Python noob here - feel free to improve it 🤓

mariusmitrofan commented 3 years ago

Thanks! Will include the changes a new PR which offers Slack integration as well.