[13:05:40] !log tools.mismatch-finder php artisan migrate && webservice restart # T321165 [13:05:43] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.mismatch-finder/SAL [13:06:58] !log tools.mismatch-finder (previous message actually by lucaswerkmeister-wmde, I forgot that the nested become would result in logging the wrong user) [13:06:58] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.mismatch-finder/SAL [13:07:54] is there a bug for that? [13:08:16] not as far as I know [13:08:21] I wouldn’t see it as a bug tbh [13:09:51] not sure how common this pattern is anyways [13:10:27] I guess it’s solvable if `become` sets a custom variable that `dologmsg` can use instead of $SUDO_USER? and a nested `become` would keep that variable intact 🤔 [15:33:25] !log glams initialization [15:33:26] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Glams/SAL [18:14:04] I never heard of nested become before. why is that even possible? (re @wmtelegram_bot: I guess it’s solvable if `become` sets a custom variable that `dologmsg` can use instead of $SUDO_USER? and a neste...) [18:14:20] but it does seem like it should be easy to fix. [18:17:09] !log sso committed a local puppet change on puppetprimary to fix upstream syncs [18:17:10] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Sso/SAL [18:18:51] !log devtools committed a local puppet change on puppetprimary to fix upstream syncs [18:18:52] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Devtools/SAL [18:22:01] !log auditlogging resolved a puppet rebase conflict to fix upstream syncs on puppetmaster03 [18:22:02] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Auditlogging/SAL [18:35:42] !log mailman resolved a puppet rebase conflict to fix upstream syncs on mailman-puppetmaster [18:35:43] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Mailman/SAL [18:36:21] you can add one tool as a member of another, so that any member of the other tool can access the first one (re @jeremy_b: I never heard of nested become before. why is that even possible?) [18:38:38] !log wikidata-query committed a local labs/private change on wdqspuppet to get puppet syncing again [18:38:39] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikidata-query/SAL [18:42:42] could add a feature to striker instead to know about groups? or is there some way to do this in ldap? [18:42:43] [18:42:45] anyway status quo doesn't sound horrible and the log issue should be easy to fix. (on phone now so not looking myself now. maybe I have time this weekend) (re @lucaswerkmeister: you can add one tool as a member of another, so that any member of the other tool can access the first one) [18:43:40] I didn’t ask for it to be fixed [18:43:54] if you want something to do, go ahead I guess [18:44:13] but I was just adding a note to a log message [18:44:43] ok but it sounds fun :-)