[feature request] Add ability to show all user's "last seen" date and time on CLI with occ

[nooblag]

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
A specific user's last seen date and time can be found with sudo -u www-data php /var/www/nextcloud/occ user:lastseen <uid> but there is no capability to return this information for all users.

Describe the solution you'd like
Perhaps all --all switch for the occ command, to return list of all user's last seen date and time?

Describe alternatives you've considered
Have considered shell scripts discussed on this forum thread, but they're cumbersome.

Additional context
Add any other context or screenshots about the feature request here.

[isdnfan]

existing occ user:list command with little postprocessing provides exactly such report
occ user:list --output=json --info| jq '.[] |{(.user_id): .last_seen}'

https://help.nextcloud.com/t/email-alerts-for-non-logged-users-more-than-30-days/157945/3

[nooblag]

Thanks, and sure, can do postprocessing (after installing jq by-the-way) or fiddle around with bash scripts to do iterating, but none of this is an ask for that.

I'm more asking for an --all switch (like other occ commands), to save all this mucking around 😃

[joshtrichards]

Given occ is already a command line tool... doing a little additional "mucking around" using broadly accepted tools (like jq) would seem the solution.

I doubt this Issue will get any traction if you wait for someone else to implement it - since there is a perfectly reasonable solution/alternative and there are "a million" other items (that don't have alternatives) that will always take core developer priority. :-)

Both the json output support and jq were basically made for this sort of use case.

You're welcome to to implement a built-in --all parameter, however, if it's that important to you. Feel free to do so and submit a PR. :-)

[nooblag]

Okay cool, here's a PR for it.