Ian Wienand 1e2ea795c2
logrotate: don't use filename to generate config file
I noticed on our hosts some logrotate files named '*.1234.conf' --
these are coming from callers of logrotate role specifying
'/var/log/program/*.log', where the '*' is turning into a literal
filename.  I didn't really consider this case.

Having a file-name starting with '*' may technically be fine, but is a
bad idea for everyone's sanity and it's potential to foot-gun some
sort of operation that suddenly wipes out a lot more than you wanted
to.

Let's just use the hash of the name to be unambiguous and still
idempotent.  Make it more git-ish by using the same 7 digits as a
default short-hash.

Change-Id: I13d376f85a25a7b8c3a0bc0dcbabd916e8a9774a
2023-02-14 07:03:17 +11:00
..
2022-02-25 17:27:35 +11:00
2022-02-18 21:39:27 +00:00
2022-08-18 14:12:30 -07:00
2022-06-28 18:41:17 +10:00
2021-12-04 10:49:11 -08:00
2022-09-27 20:33:33 +00:00
2019-02-01 10:12:51 -08:00
2022-09-15 19:21:33 -07:00
2022-02-01 13:52:47 -08:00
2022-02-10 13:24:42 -08:00
2022-02-01 13:52:47 -08:00
2019-02-25 13:14:51 -08:00
2022-10-20 09:00:43 +11:00