[jira] [Commented] (FINERACT-1238) Automated Demo Data creation tooling

["Michael Vorburger (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FINERACT-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225748#comment-17225748 ] 

Michael Vorburger commented on FINERACT-1238:
---------------------------------------------

[~bgowda] since I've seen how easy this should be with just basic Postman alone (it can do loops, and has nice macros for demo data, like random fake names and such), my suggestion is actually to simply use that, instead of a (more complicated) ETL from e.g. an Excel sheet.

> Automated Demo Data creation tooling
> ------------------------------------
>
>                 Key: FINERACT-1238
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1238
>             Project: Apache Fineract
>          Issue Type: New Feature
>            Reporter: Michael Vorburger
>            Priority: Major
>
> It would be nice, and very useful, if we had a reasonably easy way to automatically "create Demo Data" for Fineract. This makes sense both for scale testing, but perhaps even more importantly in the short term, to have local dev and demo instances like https://www.fineract.dev which are "not so empty" as they normally are. 
> This has come up e.g. on https://github.com/openMF/web-app/pull/1256 as on argument why the https://github.com/openMF/web-app/ maintainers still prefer using the old https://staging.mifos.io instead of https://www.fineract.dev.
> FINERACT-1170 is related to this, but this is more specific & focused - a pre-requisite for that, really.
> There are 2 dimensions here: WHAT to create, and HOW to create it.
> Re. WHAT, it would be good to have someone help with specifying this.. could even be a simple as a list of bullet points in an email thread?
> Re. HOW, I can think of a few options, and maybe others can think of more:
> A. SQL scripts from dump of an existing installation. I personally don't like this very much, because such dumps could contain anything - not what the REST API programmatically created, but what people providing such a dump fiddled around with in the DB.
> B. JSON files to feed the REST API, e.g. a Collection of example Postman scripts that create "one of", with some to be built tooling making "many like that". Or not using Postman, just... manual JSON with a bit of Java that sends it to the API using whatever Java HTTP client.
> C. Scripting for the REST API using some tool. Building this using our brand new Fineract Client Java API.
> I would like to say "let's do C." but seeing that [there still are issues with the Fineract Client Java API|https://issues.apache.org/jira/issues/?jql=project%20%3D%20FINERACT%20AND%20component%20%3D%20SDK], hacking something using a B. like approach would likely lead to results faster.
> [~aleks] how much more than me :P do you understand of the "functionality" to possibly help on this front?
> [~ptuomola] any thoughts about this? Do you have any interest (time) to do anything on this front?
> [~edcable] how did you traditionally populate demo instances?
> [~jdailey] ([~jamespdailey]?) is this something you would enjoy helping with?
> Anyone else reading this wanting to jump on helping with this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)