This video outlines essential best practices for Azure Synapse CI/CD pipelines to ensure efficient, reliable, and secure deployments across different environments.
Mind Map
点击展开
点击探索完整互动思维导图
[Music] foreign
cicd fans welcome to this video series
on synapse ICD my name is rikunya and
I'm a support escalation engineer on the
Azure synapse analytics team in
Microsoft's public documentation for
synapse ICD you will find one section
fully dedicated to the best practices
in this video we will walk you through
some of the best practices in synapse
ICD like integrating only your
development workspace with your kit repo
and preparing your pools before
deploying your artifacts across the
environments so let's watch this video
and see some of the best practices in
synapse acidity in action starting with
this first best practice git integration
when working on a multi-environment
scenario you have the workspace in Dev
uat pre-prod prod
you should all only connect
The Source environment your Dev
environment with your git repository no
other environment should be connected
all other environments should be
live mode and the reason for this is
that you don't want your git repo to get
out of sync you don't want any changes
to occur outside your Dev environment so
this is where your development happens
anything that is detected in your uat
pre-prod prod should be fixed in this
lower environment this should be a rule
of thumb in synapse ICD to have your
only your Dev environment integrated
with your git repo another best practice
your branching strategy this branching
strategy should be as simple as possible
and you should use feature branches that
will allow your developers to create new
features and Bug fixes you should use a
consistent naming convention for your
feature branches so you can easily
identify the work that is being done in
the branch if we are talking about the
new feature or a bug fix and some suggestions
suggestions
for example users
then your username
then new feature or add fixes and then
your add fix
on a multi-project environment project
project a
a
my username
new feature
one creating this based on your main
here's an example another one project B
then John
new feature
in Project B then
then
project a at
at fixes
and you should keep this simple
structure here let me show you when developing
developing
SQL script
try to organize your artifacts as much
as possible for example project
a I mean project a right
I will go for project a
keep my artifacts organized same
same
for example
project a
bring this here
and if you go
your branches in devops you should see
this organization reflected here
project a hot fixes developers new
features Project B the same thing keep this
this
folder structure this branching strategy
simple another best practice you should
keep the main branch foreign
foreign
Ty Branch this is your collaboration branch
branch
the code in this Branch should build
cleanly and should always be current why
do you need these qualities in your main
branch because you want to make sure
that any feature branch that is created
by your developers it will start from a
good version of code how can you achieve
this you can set up Branch policies in
the main branch go here to your main branch
branch
and set Branch policies here set a
minimum number of reviewers for example
any change that lands in the main branch
should come from a pull request
now if I try to do
something like this here create an artifact
artifact print
print
this will fail to commit
I want to keep my main branch clean not
allowing any developer to make direct
changes in this branch if I want to
create something here
suppose that I was fixing this notebook great
this is my fix
notebook doesn't matter here the branch
just for demonstration purpose
I'm going to commit all
merging
my art fix
with Main
I will take this three files these three artifacts
