Describe what you need us to do: Please perform a test SAR request for my user's data (bowlofeggs). The purpose of this request is both to test the SOP document and to make sure the script works for Bodhi. I did test the script in a home lab setup, but I am unable to run the playbook myself on production and who knows if my home lab was a valid test compared to production, so I would like to verify that I did everything correctly there as well.
When do you need this? (YYYY/MM/DD) The sooner the better, so I can fix any issues before more applications integrate.
When is this no longer needed or useful? (YYYY/MM/DD) If another SAR request comes in and everything goes well.
If we cannot complete your request, what is the impact? The SAR script will be untested with unknown problems.
Ran fine. The output is in:
/home/fedora/bowlofeggs/bowlofeggs-sar.tar.gz
on batcave01.
I expect we would normally email this back to the user? Or make the ticket private and attach it?
Also, is there some way to 'pretty print' the json? The one gigantic long line makes it kind anoying to look at with a editor/pager.
Let us know if there is anything more we can help with here.
Metadata Update from @kevin: - Issue assigned to kevin - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
On 05/14/2018 03:35 PM, Kevin Fenzi wrote:
Ran fine. The output is in: /home/fedora/bowlofeggs/bowlofeggs-sar.tar.gz on batcave01.
Fantastic! Would you mind chowning it to me so I can inspect it?
I don't know what I would recommend here, though I will point out that you won't always be able to attach it to the ticket in the case of non-FAS users.
Of course, e-mail isn't always a safe transport either.
@stickster do you have any recommendations here?
Also, is there some way to 'pretty print' the json?
That would be up to each application to do, but sure I could make Bodhi pretty-print it. I verified it by loading it up with Python's json module when I developed this. I made myself a task to have Bodhi pretty-print that so I don't forget, but it might be a while before I get time to do that.
Data should be readable now. ;)
On 05/14/2018 03:57 PM, Kevin Fenzi wrote:
Looks good, thanks! I think this was a success!
Once we have a few more apps in place, it would be sensible to do a couple more test runs. Thanks for testing this for me!
If we're not worried about the returned components being too large, email should suffice. If it's too large for that, it's acceptable to post in a way that only the requestor can access such as a password. It's not OK to post it in a way it could be read by the public.
Note that pretty printing isn't required. No problem if someone wants to do it, but the requirement is for a machine readable format.
Log in to comment on this ticket.