Similar to #6 but to manage Pulumi state backends.
The possible backend options are:
- Local Backend: the only avaiable one; singleton; just uses the currently configured Pulumi CLI;
- Project Backend: the backend that should be the default one; singleton; it stores the Pulumi state of the component instance (and history?) in the database of the corresponding project;
- Pulumi Cloud: we should support liking Pulumi accounts to store instance states in Pulumi Cloud since someone may found it useful;
- S3: just for completeness, we also should support using arbitrary S3 buckets (not only AWS).
Similar to #6 but to manage Pulumi state backends.
The possible backend options are: