86e959af67
* Initial commit for scenario tester arm deployment * Initial commit for deployment of Scenario Tester through an ARM Template * Some improvements: Event hub Id detection based in if it is a iot device or not * Add smart is data bricks function * Error fix: connection string property was not correctly set * Initial commit for deployment scripts and utilities * Deploy a default parameter file * Configure properly a system identity to the new scenario tester app + grant access to the service key vault. Do the same for spark keyvault as well. Make the app always on too. * Retrieve most of the information in the deployment resources existing in the environment already * Fix some errors in the script and template. Load from package was not really supported and there was a typo in the template. * typo fix in blob storage uri * Use the correct connection string from the array * Adding missing entries into the spark kv + make cert validation an argument to the deployment script entrypoint * Pass key vault names as parameters to json deployment file + make data bricks token resource conditional to the environment spark type * Add comments for deployment scripts for scenario tester. * Add a few more details * Add basic readme file for scenario tester directory * Enrich readme even further |
||
|---|---|---|
| .. | ||
| Resources | ||
| README.md | ||
| ScenarioTestDatabricks.json | ||
| ScenarioTestHDInsights.json | ||
| deployResources.ps1 | ||
| utilities.psm1 | ||
README.md
Scenario Tester
Scenario Tester is a tool that proactively performs http calls to data-accelerator backend and asserts that the expected output is returned by running a set of user-defined scenario runs. Each scenario is run periodically and results are tracked and stored in a database.
Install
Prerequisites
From cloud installation steps link retrieve the used inputs from common.parameters.txt and admin.parameters.txt and from deployed data-accelerator resources. Specifically we require the following:
- SubscriptionId: Subscription guid where data-accelerator was previously deployed
- TenantId: Tenant where the subscription belongs to
- ResourceGroup: Resource group where data-accelerator was previously deployed
- Application id and secret: Service principal id and secret used in the admin steps
- Keyvault base name prefix: Prefix chose by the data-accelerator deployment script. You can look for the prefix manually by looking at the data-accelerator current keyvault secret names
Steps
Execute deployResources.ps1, for example:
deployResources.ps1 -tenantId $tenantId -subscriptionId $subscriptionId -resourceGroupName $rg -applicationId $appId -appSecretKey $appSecret -kvBaseNamePrefix $kvPrefix
Development
Add your scenario creating a new class inheriting IJob and place it at Jobs directory. Then register your scenario in JobRunner class.