Azure DevOps YAML templates
Ғылым және технология
Following my previous video I will show how to optimize the CD pipeline YAML by moving the repeatedly inserted stage-yaml to a template. This makes the main stuff re-usable.
00:00:00 Recap
00:02:20 Templates
00:18:10 Trying it out
00:19:57 Trying variables in templates (failed)
00:24:37 Outro
Пікірлер: 12
Really good video! Was useful to see an implementation of templates. Looks like you can do a “Variable templates with parameter” which would then allow for the use of parameters as variables. Although I’m not sure if that would allow for a transitive binding of parameters to the outer scope
BURGIR!
Thanks Alexander, good overview of changing to use templates. But why do you have two variables (Environment and StageShort) that do the same thing?
@real-codingfreaks
Жыл бұрын
Hi. One is the ADO environment name and the other is the resource suffix in Azure.
Hi Alex, good video. I think you can declare variables in your template under the jobs level...not at the root level like you tried. So you would have variables that are valid only at the jobs scope.
@real-codingfreaks
Жыл бұрын
Yes I learned that too. It is still a mess to bring all of this together but I‘m getting better at it. Thanks!
great video, thanks, one question what extention are you using that changes the icons in vscode? like the pipeline icon to a rocket ?
@real-codingfreaks
7 ай бұрын
Vscode-icons
@wassellaouini
7 ай бұрын
thanks 💙@@real-codingfreaks
Thanks Alex, I'm following your instructions. I need your opinion on a topic. We have a SaaS platform with multi-instance architecture. I'm trying to set up a pipeline to deploy all resources for one client. Some of the clients has extra resources like more storage. How should it be done? Is there an out of the box solution in bicep for this?
@real-codingfreaks
Жыл бұрын
What do you mean by SaaS? Function Apps? Separate obe for each client? Need more info.
@tamerberatcelik7797
Жыл бұрын
@@real-codingfreaksSchmidt for each client we have two app services, one database, one frontdoor and other related resources. By SaaS I meant that we're selling the software and we install a new instance of the software with all resources for every client. And as I said, some clients has extra resources than others like a second database or a second storage blob.