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
I changed the archive_threshold to 37 in the configuration.yaml. Afterwards I rebuilt the destalinator Docker image, run it and entered the container. In the container I run the warner.py, which send a message to the concerned channels in the Slack.
The message in #general was:
Hey, heads up -- the following channels are stale and will be archived if no one participates in them over the next 30 days
The message in the concerned channels ended with
.If we don't hear from anyone in the next 30 days, this channel will be archived.
I was expecting to see 7 days instead of 30 days in those messages.
Extract of the con figuration.yaml:
# Days of silence before we warn a channel it's going to be archived
warn_threshold: 30
# Days of silence before we auto-archive a channels
archive_threshold: 37
The text was updated successfully, but these errors were encountered:
Recommend they are either hard-coded everywhere (i.e. not a parameter at all) or templated. Parameters are clearly more user-friendly. For our company slack we would prefer to have a shorted archive threshold (warn, and then archive quickly, not give another 30 days).
h3h
changed the title
archive_threshold is always considered as 30 days even if changed
Channel warning and closure messages should be templated
Mar 13, 2021
Hi,
I changed the archive_threshold to 37 in the configuration.yaml. Afterwards I rebuilt the destalinator Docker image, run it and entered the container. In the container I run the warner.py, which send a message to the concerned channels in the Slack.
The message in #general was:
The message in the concerned channels ended with
I was expecting to see 7 days instead of 30 days in those messages.
Extract of the con figuration.yaml:
The text was updated successfully, but these errors were encountered: