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
You can use any [IANA time zone](https://www.iana.org/time-zones) (as originally specified
496
+
in [PEP 615](https://peps.python.org/pep-0615/)) as part of your rules definition.
497
+
Powertools takes care of converting and calculate the correct timestamps for you.
498
+
499
+
When using `SCHEDULE_BETWEEN_DATETIME_RANGE`, use timestamps without timezone information, and
500
+
specify the timezone manually. This way, you'll avoid hitting problems with day light savings.
501
+
494
502
## Advanced
495
503
496
504
### Adjusting in-memory cache
@@ -649,11 +657,13 @@ The `action` configuration can have the following values, where the expressions
649
657
650
658
For time based keys, we provide a list of predefined keys. These will automatically get converted to the corresponding timestamp on each invocation of your Lambda function.
| CURRENT_TIME_UTC | The current time, 24 hour format (HH:mm) |
655
-
| CURRENT_DATETIME_UTC | The current datetime ([ISO8601](https://en.wikipedia.org/wiki/ISO_8601)) |
656
-
| CURRENT_DAY_OF_WEEK_UTC | The current day of the week (Monday-Sunday) |
662
+
| CURRENT_TIME | The current time, 24 hour format (HH:mm) |
663
+
| CURRENT_DATETIME | The current datetime ([ISO8601](https://en.wikipedia.org/wiki/ISO_8601)) |
664
+
| CURRENT_DAY_OF_WEEK | The current day of the week (Monday-Sunday) |
665
+
666
+
If not specified, the timezone used for calculations will be UTC.
657
667
658
668
**For multiple conditions**, we will evaluate the list of conditions as a logical `AND`, so all conditions needs to match to return `when_match` value.
0 commit comments