-
Notifications
You must be signed in to change notification settings - Fork 156
fix(logger): POWERTOOLS_LOGGER_LOG_EVENT precedence is respected #1015
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
Changes from 4 commits
6c70a0b
a034a60
0dd4568
076660c
00f5f73
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -38,9 +38,8 @@ const injectLambdaContext = (target: Logger | Logger[], options?: HandlerOptions | |
if (options && options.clearState === true) { | ||
persistentAttributes.push({ ...logger.getPersistentLogAttributes() }); | ||
} | ||
if (options) { | ||
logger.logEventIfEnabled(request.event, options.logEvent); | ||
} | ||
const logEvent = options ? options.hasOwnProperty('logEvent') ? options.logEvent : undefined : undefined; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is Node 12 support actually needed? Active support for it ended over a year and a half ago and even extended security support for it ended 2 months ago. It's now officially past EOL. That said, I don't have insight into how many Node12 Lambdas are still running, so maybe supporting existing functions makes it worthwhile. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hello @bilalq, yes. For the time being we are committed to support Node.js 12.x since AWS Lambda still supports that runtime. So far, and aside from these minor changes in some lines, it hasn't been a blocker for us, so we still see value in allowing those customers who might have not migrated to newer and actively maintained runtimes to use the Powertools utilities.
dreamorosi marked this conversation as resolved.
Show resolved
Hide resolved
|
||
logger.logEventIfEnabled(request.event, logEvent); | ||
}); | ||
}; | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
import { injectLambdaContext, Logger } from '../../src'; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (nit) missing Copyright header? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. None of the functions in that group of e2e tests has the copyright header, should I add it? |
||
import { Context } from 'aws-lambda'; | ||
import middy from '@middy/core'; | ||
|
||
type LambdaEvent = { | ||
invocation: number | ||
}; | ||
|
||
const logger = new Logger(); | ||
|
||
const testFunction = async (event: LambdaEvent, context: Context): Promise<{requestId: string}> => ({ | ||
requestId: context.awsRequestId, | ||
}); | ||
|
||
export const handler = middy(testFunction) | ||
.use(injectLambdaContext(logger)); |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,110 @@ | ||
// Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. | ||
// SPDX-License-Identifier: MIT-0 | ||
|
||
/** | ||
* Test logger basic features | ||
* | ||
* @group e2e/logger/logEventEnvVarSetting | ||
*/ | ||
|
||
import path from 'path'; | ||
import { App, Stack } from 'aws-cdk-lib'; | ||
import { v4 } from 'uuid'; | ||
import { | ||
createStackWithLambdaFunction, | ||
generateUniqueName, | ||
invokeFunction, | ||
isValidRuntimeKey | ||
} from '../../../commons/tests/utils/e2eUtils'; | ||
import { InvocationLogs } from '../../../commons/tests/utils/InvocationLogs'; | ||
import { deployStack, destroyStack } from '../../../commons/tests/utils/cdk-cli'; | ||
import { | ||
RESOURCE_NAME_PREFIX, | ||
STACK_OUTPUT_LOG_GROUP, | ||
SETUP_TIMEOUT, | ||
TEST_CASE_TIMEOUT, | ||
TEARDOWN_TIMEOUT | ||
} from './constants'; | ||
|
||
const runtime: string = process.env.RUNTIME || 'nodejs16x'; | ||
|
||
if (!isValidRuntimeKey(runtime)) { | ||
throw new Error(`Invalid runtime key value: ${runtime}`); | ||
} | ||
|
||
const uuid = v4(); | ||
const stackName = generateUniqueName(RESOURCE_NAME_PREFIX, uuid, runtime, 'LogEventEnvVarSetting-Middy'); | ||
const functionName = generateUniqueName(RESOURCE_NAME_PREFIX, uuid, runtime, 'LogEventEnvVarSetting-Middy'); | ||
const lambdaFunctionCodeFile = 'logEventEnvVarSetting.middy.test.FunctionCode.ts'; | ||
|
||
const integTestApp = new App(); | ||
let logGroupName: string; // We do not know it until deployment | ||
let stack: Stack; | ||
|
||
describe(`logger E2E tests log event via env var setting (middy) for runtime: ${runtime}`, () => { | ||
|
||
let invocationLogs: InvocationLogs[]; | ||
|
||
beforeAll(async () => { | ||
// Create and deploy a stack with AWS CDK | ||
stack = createStackWithLambdaFunction({ | ||
app: integTestApp, | ||
stackName: stackName, | ||
functionName: functionName, | ||
functionEntry: path.join(__dirname, lambdaFunctionCodeFile), | ||
environment: { | ||
LOG_LEVEL: 'INFO', | ||
POWERTOOLS_SERVICE_NAME: 'logger-e2e-testing', | ||
UUID: uuid, | ||
|
||
// Enabling the logger to log events via env var | ||
POWERTOOLS_LOGGER_LOG_EVENT: 'true', | ||
}, | ||
logGroupOutputKey: STACK_OUTPUT_LOG_GROUP, | ||
runtime: runtime, | ||
}); | ||
|
||
const result = await deployStack(integTestApp, stack); | ||
logGroupName = result.outputs[STACK_OUTPUT_LOG_GROUP]; | ||
|
||
// Invoke the function twice (one for cold start, another for warm start) | ||
invocationLogs = await invokeFunction(functionName, 2, 'SEQUENTIAL'); | ||
|
||
console.log('logGroupName', logGroupName); | ||
|
||
}, SETUP_TIMEOUT); | ||
|
||
describe('Log event', () => { | ||
|
||
it('should log the event on the first invocation', async () => { | ||
dreamorosi marked this conversation as resolved.
Show resolved
Hide resolved
|
||
const firstInvocationMessages = invocationLogs[0].getAllFunctionLogs(); | ||
let eventLoggedInFirstInvocation = false; | ||
for (const message of firstInvocationMessages) { | ||
if (message.includes(`event`)) { | ||
eventLoggedInFirstInvocation = true; | ||
expect(message).toContain(`"event":{"invocation":0}`); | ||
} | ||
} | ||
|
||
const secondInvocationMessages = invocationLogs[1].getAllFunctionLogs(); | ||
let eventLoggedInSecondInvocation = false; | ||
for (const message of secondInvocationMessages) { | ||
if (message.includes(`event`)) { | ||
eventLoggedInSecondInvocation = true; | ||
expect(message).toContain(`"event":{"invocation":1}`); | ||
} | ||
} | ||
|
||
expect(eventLoggedInFirstInvocation).toBe(true); | ||
expect(eventLoggedInSecondInvocation).toBe(true); | ||
|
||
}, TEST_CASE_TIMEOUT); | ||
|
||
}); | ||
|
||
afterAll(async () => { | ||
if (!process.env.DISABLE_TEARDOWN) { | ||
await destroyStack(integTestApp, stack); | ||
} | ||
}, TEARDOWN_TIMEOUT); | ||
}); |
Uh oh!
There was an error while loading. Please reload this page.