Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Salesforce DevOps for Architects

You're reading from   Salesforce DevOps for Architects Discover tools and techniques to optimize the delivery of your Salesforce projects

Arrow left icon
Product type Paperback
Published in Jan 2024
Publisher Packt
ISBN-13 9781837636051
Length 260 pages
Edition 1st Edition
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Rob Cowell Rob Cowell
Author Profile Icon Rob Cowell
Rob Cowell
Lars Malmqvist Lars Malmqvist
Author Profile Icon Lars Malmqvist
Lars Malmqvist
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Chapter 1: A Brief History of Deploying Salesforce Changes 2. Chapter 2: Developing a DevOps Culture FREE CHAPTER 3. Chapter 3: The Value of Source Control 4. Chapter 4: Testing Your Changes 5. Chapter 5: Day-to-Day Delivery with SFDX 6. Chapter 6: Exploring Packaging 7. Chapter 7: CI/CD Automation 8. Chapter 8: Ticketing Systems 9. Chapter 9: Backing Up Data and Metadata 10. Chapter 10: Monitoring for Changes 11. Chapter 11: Data Seeding Your Development Environments 12. Chapter 12: Salesforce DevOps Tools – Gearset 13. Chapter 13: Copado 14. Chapter 14: Salesforce DevOps Tools – Flosum 15. Chapter 15: AutoRABIT 16. Chapter 16: Other Salesforce DevOps Tools 17. Chapter 17: Conclusion 18. Index 19. Other Books You May Enjoy

Org-dependent packages

The other type of unlocked package that Salesforce provides, org-dependent packages, tackles the problem of dependencies by deferring compilation and validation of your changes until installation time. This means that these dependencies don’t necessarily need to be in your development org or in your source control for you to build the package – you can depend on metadata that exists in the target org.

This type of unlocked package is ideal for Salesforce orgs that are large, complex, and have been in use for a long time and thus have accumulated a lot of changes. Unpicking these changes into separate modules is lengthy, challenging work, but by having a package type that is able to depend on unpackaged metadata in the target org, you can defer (or even avoid) the need to refactor your entire org.

Creating an org-dependent package is incredibly simple, too – the command is the same as that for creating an unlocked package, but with the...

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 €18.99/month. Cancel anytime