When you deploy a Cloud Assembly blueprint, one component might need another component to be available first.
How to create an explicit dependency
Sometimes, a component needs another to be deployed first. For example, a database server might need to exist first, before an application server can be created and configured to access it.
An explicit dependency sets the build order at deployment time, or for scale in or scale out actions. You can add an explicit dependency using the graphical design canvas or the code editor.
Design canvas option—draw a connection starting at the dependent component and ending at the component to be deployed first.
Code editor option—add a
dependsOnproperty to the dependent component, and identify the component to be deployed first.
An explicit dependency creates a solid arrow in the canvas.
How to create an implicit dependency
Sometimes, a component property needs a value found in a property of another component. For example, a backup server might need the operating system image of the database server that is being backed up, so the database server must exist first.
Also called a property binding, an implicit dependency controls build order by waiting until the needed property is available before deploying the dependent component. You add an implicit dependency using the code editor.
Edit the dependent component, adding a property that identifies the component and property that must exist first.
An implicit dependency creates a dashed arrow in the canvas.