Introduction

One of the issues for making both demonstrations, PoCs, and onboarding more difficult is not having a pre-created set of converts and data for common use cases that clients can easily use and learn with. The move to create good demonstration data has been started and will continue to progress with data of different types, formats, and packaging.

The next step is a way to easily deploy this data and coinciding converts to target instances. Ability to easily present clients with data and converts, will allow for easier walk-throughs with documentation as well to see a path of processing.

It can also be added into CICD to test UI functionality and to test with “canned” data to make sure the application is functioning as expected.

Location

The scripts are found at bettrdata-infra/scripts/demo_data_loader

Deployment Artifacts

Deployment for customers will consist of two main areas, deployment of data and deployment of converts/schemas

Data Deployment

Data will be stored in a common repository that will be accessible and pre-configured for all instances. Presently, data is being stored in S3, but other source data locations could be added as needed. The repository will allow for deploying a set of data that is related to a particular use case.

Convert Deployment

In the same way, having a set of configurations for a convert related to a use case would be kept in a common repository and capable of being deployed to the instance by the client. Deployment of configurations would consist of:

• The convert/schema
• Related fields for the convert
• Optionally, auto-convert ability so test data will go through the process and show a template for clients to follow.

It is possible to keep the configurations locally, in a separate collection for instance. In order to do this, however, there would need to be a way to update the convert data as part of a version upgrade of an instance. Keeping the data in a separate shared location could be more beneficial in updating and adding to the data sets.

User Interaction

For this functionality, we will need to add a place in the UI where clients can choose to deploy a demo of a particular use case. The user can choose a use case that makes sense for them and then in a click add the converts and data to their instance. This would require an included set of S3 access for the data.

Presently there is the user, demo-svc, which has read and list access to the bettrdata-demo-repository. This will allow security while allowing dynamic addition to the demo data.