[almighty] a snapshot of data - evolving in time

[Aslak Knutsen]

We have 2 similar 'datasets' as well:

* Example input for cli to create workitem/workitemtypes/trackers etc etc
https://github.com/almighty/almighty-core/tree/master/examples

* UI In-memory API contract use for unit testing
https://github.com/almighty/almighty-ui/blob/master/src/app/in-memory-data.service.ts

Wondering if these could be combined into 1, e.g.

* Create executable Examples that can populate the Database via REST API
* 'Export' the Examples via REST API for use with in memory DB in UI

?

-aslak-




On Tue, Oct 11, 2016 at 8:48 PM, Leonard Dimaggio <ldimaggi at redhat.com>
wrote:

> Could we implement a database export/import function? (At some point,
> users will want to be able to archive/backup their data.)  The final step
> of a core build could be to output test data in the correct/latest schema
> into a form that can be imported.
>
> 'Opinions?,
> Len D.
>
>
> Ref: https://dzone.com/articles/exporting-and-importing-data-in-apiman
> (from the JBoss apiman project)
>
> On Tue, Oct 11, 2016 at 12:36 PM, Karanbir Singh <kbsingh at redhat.com>
> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> hi,
>>
>> in order to execute our e2e testing ( ref:
>> https://github.com/almighty/almighty-ui/issues/147 ) - we need to be
>> able to bringup the service on demand, but the db cant be blank.
>>
>> what data can we pre-load into the db for the tests to be productive ?
>>
>> how can we keep this data store updated ( so we dont hit migration
>> issues etc when core comes up ) ?
>>
>> Ideally a sql dump checked into the e2e tests code repo itself would
>> be used. But could we come up with a process that keeps this sql updated
>>  ?
>>
>> the same data would / could be used for the per-PR service bringup
>> instances.
>>
>> regards,
>>
>> - --
>> Karanbir Singh, Project Lead, The CentOS Project, London, UK
>> Red Hat Ext. 8274455 | DID: 0044 207 009 4455
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.22 (GNU/Linux)
>>
>> iQEcBAEBAgAGBQJX/RUUAAoJEI3Oi2Mx7xbtYEMIALo0OFGlm4s5FAfdS93UH0o8
>> Sve365cWE3/RoAIJc7qYr42nEmpCzfWjSU6sCPMyYRJb+C+qbZvZoTuYeQ5Hdc+A
>> SnxiWPH9rfv6MY64aCyeoXjMhz9u76c8RXadLiJNk8gF6XglMNUIaTjM1DbuMNtn
>> eCMr4K/IbuT9V9hL0v7xXN6Cdz0fRpdsrmgun2c1mm6qTno5+NicEduzsnw/ezDz
>> GVYWbY88ji2GY29vURBlqhordasv5C4RvdTS7HKdqa3drk9NrmWFZ2KsCXmD9qm3
>> bIxUeh1U1jdBQcZNmnTdPM3DYVhn74eHPH0QM1royAOzCuLopMkAS+LvN/v1JW0=
>> =QWdT
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> almighty-public mailing list
>> almighty-public at redhat.com
>> https://www.redhat.com/mailman/listinfo/almighty-public
>>
>
>
>
> --
> Len DiMaggio (ldimaggi at redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20161012/dd2d0fca/attachment.htm>