Skip to content

Commit 0d2b71b

Browse files
authored
Added linked service IR TSGs
1 parent 9bf6f01 commit 0d2b71b

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

articles/data-factory/ci-cd-github-troubleshoot-guide.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -295,6 +295,29 @@ There are several scenarios which can trigger this behavior, all of which involv
295295

296296
New runs of the parent pipeline will automatically begin succeeding, so typically no action is needed. However, to prevent these errors, customers should consider dependencies while authoring and planning deployments to avoid breaking changes.
297297

298+
### Cannot parameterize integration run time in linked service
299+
300+
#### Issue
301+
Need to parameterize linked service integration run time
302+
303+
#### Cause
304+
This feature is not supported.
305+
306+
#### Resolutio
307+
You have to select manually and set an integration runtime. You can use PowerShell API to change as well. This change can have downstream implications.
308+
309+
### Update/change Integration runtime during CI/CD.
310+
311+
#### Issue
312+
Changing Integration runtime name during CI/CD deployment.
313+
314+
#### Cause
315+
Parameterizing an entity reference (Integration runtime in Linked service, Dataset in activity, Linked Service in dataset) is not supported. Changing the runtime name during deployment will cause the depended resource (Resource referencing the Integration runtime) to become malformed with invalid reference.
316+
317+
#### Resolution
318+
Data Factory requires you to have the same name and type of integration runtime across all stages of CI/CD.
319+
320+
298321
## Next steps
299322

300323
For more help with troubleshooting, try the following resources:

0 commit comments

Comments
 (0)