---
# System prepended metadata

title: Non blocking behaviour for ordering

---

# Non blocking behaviour for ordering

## Problem statement
Resource B depends on resource A to exists and resource A depends on resource B to be ready.

## Solution
To have a non blocking behaviour with ordering, i,e if resource B depends on A, deploy resource A first and then move on to deploying resource B without waiting for the resource A to be ready.

## How do we let users switch between blocking and non blocking behaviours?
- To have a new Target Action type in a change rule (other than upserting and deleting), which lets users to switch to a non blocking behaviour.
    - How would this effect deletion?
    - How would this work with multiple resources in the target change group?
- Add a flag to to wait rules, which would tell kapp to unblock the
