You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pydantic v2 changed the accepted str format for datetime and timedelta (compared to v1).
Current status
In ENV vars, timings have different formats and sometimes, without knowing the implementation, it's not easy to understand if we are talking about seconds, mins, hours or days from simple scalar numbers.
Action
Uniform all the intervals, timeouts etc. to a standard format.
Legenda:
🚨 BREAKING CHANGE ⚠️ WARNING
DYNAMIC_SIDECAR_API_SAVE_RESTORE_STATE_TIMEOUT 🚨
After migration to Pydantic v2, it's a dt.timedelta instead of PositiveInt.
Context & Motivation
Pydantic v2 changed the accepted
str
format fordatetime
andtimedelta
(compared to v1).Current status
In ENV vars, timings have different formats and sometimes, without knowing the implementation, it's not easy to understand if we are talking about seconds, mins, hours or days from simple scalar numbers.
Action
Uniform all the intervals, timeouts etc. to a standard format.
Legenda:
🚨 BREAKING CHANGE
⚠️ WARNING
DYNAMIC_SIDECAR_API_SAVE_RESTORE_STATE_TIMEOUT
🚨After migration to Pydantic v2, it's a
dt.timedelta
instead ofPositiveInt
.Ops-Config
PROJECTS_INACTIVITY_INTERVAL
Currently, the ENV var represents seconds and is implicitily validated against timedelta but with a warning.
Ops-Config:
ENV vars that need changes
PROJECTS_INACTIVITY_INTERVAL
env var format #6797CLUSTERS_KEEPER_TASK_INTERVAL
env var #6812The text was updated successfully, but these errors were encountered: