New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ref(serverless): Remove relay extension from AWS layer #8080
Conversation
size-limit report 📦
|
c022489
to
3d02e93
Compare
@@ -46,6 +46,12 @@ async function buildLambdaLayer(): Promise<void> { | |||
'../build/npm/cjs/awslambda-auto.js', | |||
'build/aws/dist-serverless/nodejs/node_modules/@sentry/serverless/dist/awslambda-auto.js', | |||
); | |||
|
|||
const version = run("cat package.json | jq --raw-output '.version'", { stdio: 'pipe' }).trim(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
h: the jq
command errors for me locally because I don't have jq installed on my machine. Can we make sure that this doesn't become a requirement for a successful local build? I think we can either import/require the or read and JSON.parse
the package.json
instead to get the version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another idea: I just saw that read-pkg
is still registered as a dev dependency but we don't seem to use it anywhere. So we could use it to read the package.json here, too. (Or alternatively, let's get rid of it)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- removed
read-pkg
- imported
version
frompackage.json
(needed"resolveJsonModule": true
intsconfig.json
)
55ae2f5
to
234a678
Compare
we're reverting back to the older setup since the whole 'relay as AWS extension' experiment didn't really work out. * revert port override in DSN * remove gh action that bundles relay * zip in place as part of `buildLambdaLayer` part of getsentry/team-webplatform-meta#58
234a678
to
85a6e60
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adjusting, LGTM now and it builds successfully for me. Just to confirm: You testes this on AWS, right? especially the aws-auto command?
yep, tested manually, will test whole prod flow once released |
we're reverting back to the older setup since the whole 'relay as AWS extension' experiment didn't really work out.
buildLambdaLayer
part of getsentry/team-webplatform-meta#58
see python PR - getsentry/sentry-python#2068