BFD-3745: Force UTC everywhere #2498
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aschey-forpeople
requested review from
mjburling,
dondevun and
malessi
as code owners
dondevun
reviewed
Nov 22, 2024
dondevun
previously approved these changes
Nov 25, 2024
timothy-ellis-ky
previously approved these changes
Nov 26, 2024
aschey-forpeople
dismissed stale reviews from timothy-ellis-ky and dondevun
via
5cb81a5
dondevun
previously approved these changes
Dec 2, 2024
aschey-forpeople
force-pushed
the
BFD-3745
branch
from
62a8936 to
3482e73
Compare
timothy-ellis-ky
approved these changes
Dec 4, 2024
dondevun
approved these changes
Dec 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JIRA Ticket:
BFD-3745
What Does This PR Do?
This change sets
TZ=UTCeverywhere we launch a JVM process to ensure consistency with date operations. Notably this fixes the following issues:_lastUpdatedparameter without specifying a timezone, it currently defaults to the server timezone which could produce unexpected resultsWhat Should Reviewers Watch For?
If you're reviewing this PR, please check for these things in particular:
What Security Implications Does This PR Have?
Please indicate if this PR does any of the following:
Adds any new software dependencies
Modifies any security controls
Adds new transmission or storage of data
Any other changes that could possibly affect security?
I have considered the above security implications as it relates to this PR. (If one or more of the above apply, it cannot be merged without the ISSO or team security engineer's (
@sb-benohe) approval.)Validation
Have you fully verified and tested these changes? Is the acceptance criteria met? Please provide reproducible testing instructions, code snippets, or screenshots as applicable.
Tested the server locally and in an ephemeral environment to ensure the setting took effect.