hi Sergey, there's currently an issue with the LTI service deployed in QA where it's pointing to the *dev* MySQL table.  This problem is easily corrected by setting a value in the service's application properties.  With that, here are the issues at hand with a few possible solutions:

1. QA LTI pointing to DEV DB - set application property "spring.datasource.url" to the  correct JDBC URL, e.g. in DEV this value is jdbc:mysql://wpng-dev.clgqhpadyojf.us-east-1.rds.amazonaws.com/wpng, also set "spring.datasource.username" and "spring.datasource.password" to appropriate values.

2. Need a way to create Orion mapping SQL schema - I'd recommend leveraging DB migration tech (e.g. Flyway) that's easily usable in LTI service's spring-boot integration.

3.  Need a way to specifiy Orion mapping seed data - I'd also recommend using the same migration tech above for seed data.


Issues #2 and #3: Mike and myself will do that work assuming @Sergey @Vasanth, etc, agree on that approach

Issue #1: Is in Korolev team's hands I think (or whoever does QA deployments)

russ