Bug: LogFormatter Timezone about powertools-lambda-typescript HOT 5 CLOSED

From what I read online, it seems that this should be the system-wide setting which is a symlink. I am not sure Node.js is able to or can be configured to follow the link and convert it to the expected format.

If this is a test environment (but likely even if it isn't) I think the easiest way would be to set the desired timezone as environment variable in your code/entry points (process.env.TZ = 'Europe/Madrid') or when you launch your code (i.e. TZ=Europe/Madrid node foo.js).

I hope it helps!

from powertools-lambda-typescript.

Thanks for opening your first issue here! We'll come back to you as soon as we can.
In the meantime, check out the #typescript channel on our Powertools for AWS Lambda Discord: Invite link

from powertools-lambda-typescript.

Hi @springer5296, thank you for opening this issue.

Without using Powertools, what's the value of the TZ environment variable?

For example, if you run this code below, what's the output?

console.log(process.env.TZ);

We support only values that appear in the TZ column of the IANA time zone database because that's the convention that the AWS Lambda service uses.

from powertools-lambda-typescript.

Thanks for the quick response @dreamorosi! It does seem like TZ is being set to that value for some reason. I will do some digging to determine how we can get this set to a proper value in our repo.

from powertools-lambda-typescript.

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

from powertools-lambda-typescript.