Generating Config Files using CLI tool

[Shyam Sundar J (severussundar)]

Why make this change?

• Closes CLI tool: Add a script to generate the config files used in testing #471
  • Generate the config files for all database types using CLI commands
  • Remove the checked-in config files
  • Add reference config files for Cosmos and Sql

What is this change?

• Text file for each database type containing the dab commands is added in the folder ConfigGenerators

• Scripts (bash and powershell) are added that reads the command files and executes them using the DAB dll executable

• A property generateConfigFiles can be specified along with the build command to generate the config files along with the build. Exact build command : dotnet build -p:generateConfigFiles=true

• Running just dotnet build will build the entire project but skip generating the config files.

• This gives users the flexibility to generate the config files along with build if they wish to do so.

• Reference config files for Sql(dab-config.SqlReferenceConfig.json) and Cosmos(dab-config.CosmosReferenceConfig.json) are added.

• The source type has been modified in the schema to support tables, views and stored-procedures in the config.

• For local development,

  First, the right connection string needs to be updated in the init command of the respective database command files (The .txt files that contains the dab commands).

  Build should be performed using the command dotnet build -p:generateConfigFiles=true. Running this will generate the config files for all the database types.

  Now, it should be possible to start DAB. At this point, the local branch is ready to perform and validate code changes.

  After making the required code changes, a build can be performed either using dotnet build or dotnet build -p:generateConfigFiles=true. Running, just dotnet build should be fine now, as the config files are already generated, and the delta is the code changes.

  If there are changes made to the command files, then the updated config file can be generated by running the configGenerator script manually using configGenerator.ps1 <database_type>. Runnning dotnet build after that will build the project with the latest config file. Alternatively, dotnet build -p:generateConfigFiles=true can be run. It combines both the config generation and build into a single command

How was this tested?

• Existing integration tests run successfully with the generated config files
• Existing unit tests run successfully with the generated config files

Side effects of this change

• Any change to the config files will need to be done through the CLI commands

[Aniruddh Munde (Aniruddh25)]

Good starter, but looking for the actual scripts - so that it represents the customer scenario.

[Aniruddh Munde (Aniruddh25)]

LGTM, thanks for accommodating the changes to be able to generate the config files manually too.