Sequencing deployments

[ninjarobot]

ARM will deploy everything it can in parallel, and Farmer will specify dependencies with dependsOn to ensure the known dependencies are deployed in order. However, there are some cases where the author of a deployment needs certain pieces to deploy in a sequence regardless of dependencies.

We could add an operation on the arm builder where you can add certain resources in a sequence and then use that to add additional resources in dependsOn so the resulting deployment will deploy them sequentially. It's a bit higher level than managing the dependsOn directly, so it makes the intent clearer.

arm {
    add_resource_seqential [
        resource1
        resource2
        resource3
    ]
}

The result of this would be

• resource3 has a dependsOn for resource2.
• resource2 has a dependsOn for resource1.

Is this doable? There are some resource records that don't have any dependencies at all, so it may be necessary to add some sort of interface to any resource that could be supported in this list to ensure that it has dependency support.

[Thorium]

You can do this basically via this kind of pseudo template:

let fixedList = 
    resourceConfigList
    |> List.fold(fun gathered resource ->
        if resource = resourcelist.Head then
            resource :: gathered // first doesn't depend anything
        else
            { resource with //next depends the previous in the list
                Dependencies = ((gathered |> List.head) :: resource.Dependencies)
            } :: gathered) [])