Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
​Application Lifecycle Management on Microsoft Power Platform

You're reading from   ​Application Lifecycle Management on Microsoft Power Platform A comprehensive guide to managing the deployment of your solutions

Arrow left icon
Product type Paperback
Published in Oct 2024
Publisher Packt
ISBN-13 9781835462324
Length 222 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Benedikt Bergmann Benedikt Bergmann
Author Profile Icon Benedikt Bergmann
Benedikt Bergmann
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Chapter 1: An Intro to ALM FREE CHAPTER 2. Chapter 2: ALM in Power Platform 3. Chapter 3: Power Platform Environments 4. Chapter 4: Dataverse Solutions 5. Chapter 5: Power Platform CLI 6. Chapter 6: Environment Variables, Connection References, and Data 7. Chapter 7: Approaches to Managing Changes in Power Platform ALM 8. Chapter 8: Essential ALM Tooling for Power Platform 9. Chapter 9: Project Setup 10. Chapter 10: Pipelines 11. Chapter 11: Advanced Techniques 12. Chapter 12: Continuous Integration/Continuous Delivery 13. Chapter 13: Deepening ALM Knowledge 14. Assessments 15. Index 16. Other Books You May Enjoy

Exploring advanced YAML

In the first part, we will take a look at advanced YAML methods. Specifically, we will discuss variables, parameters, loops, and conditions. Those are important to make your pipeline more robust and dynamic. By using them, your pipelines can handle more or less any scenario and requirement your project could encounter. You could even easily create template pipelines for reuse in different projects, without the need to redo them for each of those projects.

Variables and parameters

So far, the pipelines we created in Chapter 10 have been very static. For example, the name of the solution was hardcoded. This means the pipeline isn’t reusable without changing some parts. Another part that usually should be dynamic is whether we want to perform an update or upgrade when importing solutions, or use settings files or not.

We will learn more about settings files in the next section.

When it comes to pipelines, there are two different types of dynamic...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image