Forum Discussion
Data Pipeline Copy Data Update source using Deployment Rules
- 1 year ago
Hi,
To resolve the above problem we are planning to perform following steps:Step 1: Create 2 separate connections inside Fabric "Manage Connections and Gateway" say SalesDB_Dev and SalesDB_Test and keep note of both the Connection Ids.
Step 2: Create new Data Pipeline with CopyData action with SalesDB_Dev connection configured as Source and Lakehouse configured as Sink.
Step 3: Enable GIT Integration on Dev Workspace and sync the content with app_dev branch.
Step 4: Create new branch app_test branch out of app_dev branch to have all the synced code to app_test branch.
Step 5: Open the pipeline code file i.e. "pipeline-content.json" and update the connection id from SalesDB_Dev to SalesDB_Test. For reference
"externalReferences": { "connection": "d350327d-50da-4947-a9b2-f61ab33e1d37" },Step 6: Enable GIT Integration on Test Workspace to sync the content from app_test branch.
Step 7: Once sync completes, validate the connection in the pipeline copydata action and it should refer to SalesDB_Test.
Once the above approach seems to be working fine and there is no issue/challenge in going with this, we can automate the process of updating the connection id in pipeline-content.json and syncing to respective workspace using Fabric API through ADO pipelines.
Do revert in case anyone see any challenge/issue in this.
Hi,
To resolve the above problem we are planning to perform following steps:
Step 1: Create 2 separate connections inside Fabric "Manage Connections and Gateway" say SalesDB_Dev and SalesDB_Test and keep note of both the Connection Ids.
Step 2: Create new Data Pipeline with CopyData action with SalesDB_Dev connection configured as Source and Lakehouse configured as Sink.
Step 3: Enable GIT Integration on Dev Workspace and sync the content with app_dev branch.
Step 4: Create new branch app_test branch out of app_dev branch to have all the synced code to app_test branch.
Step 5: Open the pipeline code file i.e. "pipeline-content.json" and update the connection id from SalesDB_Dev to SalesDB_Test. For reference
"externalReferences": {
"connection": "d350327d-50da-4947-a9b2-f61ab33e1d37"
},Step 6: Enable GIT Integration on Test Workspace to sync the content from app_test branch.
Step 7: Once sync completes, validate the connection in the pipeline copydata action and it should refer to SalesDB_Test.
Once the above approach seems to be working fine and there is no issue/challenge in going with this, we can automate the process of updating the connection id in pipeline-content.json and syncing to respective workspace using Fabric API through ADO pipelines.
Do revert in case anyone see any challenge/issue in this.
Looks like a plan that theoretically could work. I've tried to code a pipeline parameter in the connection part of the json code, but that did not work. A hard-coded connection id may work. I'm interested too. Please ley us know how it went.