Synapse CI/CD: Using a custom parameter template
Вставка
- Опубліковано 9 бер 2023
- Hello Synapse CI/CD fans! In the third video of our Synapse CI/CD series, Rui walks you through how you can take advantage of custom template parameterization when deploying your Synapse artifacts to a target environment.
To watch all of the videos in this series, check out the Synapse CI/CD playlist: • Synapse CI/CD
00:06 Introduction
01:30 Demo
16:35 Wrap-Up
Azure Synapse Analytics Community site: aka.ms/SynapseUser
Join the Azure Synapse Influencer program!
aka.ms/SynapseInfluencer
Rui's Twitter: / _azurui_
Synapse Twitter: / azure_synapse
#azuresynapse #cicd
This is excellent series. Thank you
Love your video, but somehow, I can hear a noise. It starts around 1:32 - at the beginning of the demo.
What if you have multiple pipelines created in Synapse Workspace? How do you parameterize each especially when multiple pipelines have the same parameter names?
Rui❤
Hi Rui, thanks for the video, i have setup it in my account, but we are using Selfhosted IR, i am not able to parametrize this, how can i skip self hoste ir from deployment and just make it refer in UAT ENV??
Hi Rui, is there a way to access these parameter values from the Library Variable groups?
Hello Rui! I've a question... How do you think I should go forward in order to deploy an SQL script? Imagine that I have SQL script with a create external table statement or a create SQL table and I want to create the table in the new workspace. How can I do it?
Great video, you saved my life with the custom parameter template!
Hey Francisco, Sql scripts are not meant to be use to deploy database changes across environments. Consider automating the deployment of your database changes using DACPAC (there's a video in this playlist covering that 😉)
@@thefabricbuddy Can you please provide the link that point directly to DACPAC please ?
How to parameterize Synapse pool name, Self hosted IR name as a parameter?
by adding the "name" property to the corresponding artifact definition will allow you to parameterize the artifact name:
here's an example below that will allow you to parameterize the Integration Runtime name.
"Microsoft.Synapse/workspaces/integrationRuntimes": {
"name":"=",
"properties": {
"typeProperties": {
"*": "="
}
}
},
if we have 20 different note books?
then should we have somany
Same question I too have, every time we keep adding new note books..
@@paramesh4881 I ended up making a bash script prior to the Synapse Deploy task to rename parameter values, as the MS spec to rename stuff is clunky.
@@MikeHowles Hi Mike, how are you? I'm trying the same approach as you, but using Powershell it seems that my automation didn't work, I'm having errors when deploying and this is very strange because my automation is correct, the parameters are being changed. Can you help me with this?