A question about the mechanics of the `parent` Resource Option: I run into situations where something that would logically be the child of a given resource, like an Azure Network Interface being a child of a Virtual Machine. However, due to how I need to pass information around in my stack, I must create the Network Interface before the thing that would be its parent Virtual Machine. When this happens, I can't specify that the Parent of the Network Interface is the Virtual Machine, because the variable that contains the Virtual Machine doesn't yet exist. Would it be reasonable to request a new `child`/`children` Resource Option, allowing resources to declare their children, to accommodate these situations?