integrationtests README.md: Changed SQL related variables' naming to align with Synapse style
integrationtests devcontainer .envtemplate : Changed SQL related variables' naming to align with Synapse style
Code changes
Created and stored service principal for Synapse integration testing at key vault and azdo variable groups
Stored Synapse SQL related credential info at key vault and azdo variable groups, also changed to Synapse naming
file list
infrastructure/main.bicep
infrastructure/modules/synapse.bicep
scripts/deploy_infrastructure.sh
scripts/deploy_azdo_variables.sh
scripts/init_environment.sh
Test changes
Changed SQL related variables' naming to align with Synapse style
file list:
integrationtests/tests/conftest.py
integrationtests/tests/dataconnectors/sql.py
CI-CD changes
Add job template: integration-tests-job.yml
Modify job template: deploy-dedicated-sql-pool-job.yml, changed to new Synapse sql azdo variable names
Modify azure-pipelines-cd-release.yml: add integration-testing section at "STG" stage
Purpose
Create service principal for Synapse version of integration testing
Enable Synapse Dedicated SQL pool related configuration E2E
Enable integration testing at current CD pipeline
Does this introduce a breaking change? If yes, details on what can break
Author pre-publish checklist
[x] Added test to prove my fix is effective or new feature works
[x] No PII in logs
[x] Made corresponding changes to the documentation
Validation steps
1. run deploy.sh
Checked key vault had corresponding secrets being created
Synapse RBAC also being granted to certain service principal:
Checked AZDO variables being created
2. trigger ci/cd pipelines on AZDO
For integration testing successes at AzDo, temporarily tested at DEV environment since there is no steps deploying Synapse artifacts to STG environment for now, and temporary configured dependsOn: deploy_dedicated_sql_pool, but in the code itself, already configured as dependsOn: deploy_synapse (deploy job name)
Expected Result:
AZDO pipeline (integration testing part) success
The actual Synapse pipelined had being triggered and ran completed
Type of PR
Purpose
Does this introduce a breaking change? If yes, details on what can break
Author pre-publish checklist
Validation steps
1. run deploy.sh
2. trigger ci/cd pipelines on AZDO For integration testing successes at AzDo, temporarily tested at DEV environment since there is no steps deploying Synapse artifacts to STG environment for now, and temporary configured dependsOn: deploy_dedicated_sql_pool, but in the code itself, already configured as dependsOn: deploy_synapse (deploy job name)
Expected Result: AZDO pipeline (integration testing part) success The actual Synapse pipelined had being triggered and ran completed
Issues Closed or Referenced