We should expose a method for Terraform code to run alongside components - with in-cluster state? - so component apply actions can invoke these modules to i.e. create AWS resources or deploy Vault policies. These should also be able to wait on the component to finish applying before they run

-and drop the current "component universal ID" system. this would simplify things a lot, just don't allow the registration of two components with the same stringified name... one name per component per namespace

Some components need to be directly applied before FluxCD - for example if FluxCD itself is being installed (bootstrapped) before the rest of the resources get applied

add a this.assert() function to run simple checks during the build phase of a component

Store non-secret component values inside the cluster using a ConfigMap. This will allow component references to be made from configurations independent of the main cluster configuration. (We could store the cluster's Facts here too)

Instead of configuring components globally, allow passing in a component instance that can be referenced later. This will allow duplicate instances of the same component to coexist in the same cluster configuration.