On Mon, 25 Sep 2017 05:37:03 -0400
Harold Dost <harolddost(a)gmail.com> wrote:
Assuming that the schema  is correct, there should be no personal
or secret information. Though it would be good to validate that there
aren't any unexpected tables.
That schema was correct in the past but has not been kept up to date
That being said, none of the changes I can think of would cause a
problem in making the database dump public.
Harold Dost | @hdost
On Sep 25, 2017 01:30, "Dan Callaghan" <dcallagh(a)redhat.com> wrote:
Is there any objection to making the ResultsDB database dumps public
I wanted to grab a database dump today, to populate a local database
for development purposes. I was able to scp it from db-qa02 since I'm
in sysadmin-qa, but I figured it would be nice to have it available
publicly alongside those other applications' db dumps.
I can't think of any reason why the ResultsDB dumps need to be kept
secret. There should be no sensitive data in them, right?
So if there are no objections I'll file an infra ticket for adding the
dumps into the public-db-copy script.
Dan Callaghan <dcallagh(a)redhat.com>
Senior Software Engineer, Products & Technologies Operations
qa-devel mailing list -- qa-devel(a)lists.fedoraproject.org
To unsubscribe send an email to qa-devel-leave(a)lists.fedoraproject.org