Here's a list of things which should be implemented going forward. This is in no particular order at the moment.
- Allow for multiple instances in same account/resource group. Right now, resources do not have a unique name and they should. Using the random provider as done with the AWS VPC already.
- Allow cluster installs on Azure (AWS is working, see below).
- Allow for certs to be pushed to cloud storage, once requested/installed.
- Allow more than one clouds at the same time as
prepare.sh
suggests. Right now, this does not work as it requires only ONErequired_providers
block but both template files introduce an individual one. Should be addressed by making this smarter, introducing aversions.tf
file which is built byprepare.sh
. See https://discuss.hashicorp.com/t/best-provider-tf-versions-tf-placement/56581/5
- Work around 16kb user data limit in AWS (seems to not be an issue in Azure).
- Allow cluster installs (e.g. multiple computes, adding a VPC cluster network). Works on AWS, thanks to amieczko.
- Allow to use an already existing VPC