Yeah I guess a lot of the orchestration can be effectively handled by terraform, I get what you mean regarding cloud primitives. This is my next step to seeing

Yeah I guess a lot of the orchestration can be effectively handled by terraform, I get what you mean regarding cloud primitives. This is my next step to seeing how this can work in a production environment. Instead of an ingress you can use ELB, for instance. I guess this means your environment is very "native" to a specific cloud however and not as easily transferrable. One thing I did like about k8s is that it's easy to self-host with microk8s but tbh, I think in production you'd be using a cloud provider's managed k8s (e.g. AKS) anyway. Looking at how to attach/configure a ElastiCache, RDS, or some EFS to a project also. What's the best way to runtime configure an image when you create it as an instance? I couldn't see any options on ops instance create for environment variables or anything like that but this also seems like, weird - IE you wouldn't give a VM environment variables, but with a normal EC2 instance there's an agent that handles this sort of thing. Would you have to bake the configuration into the image? Also how does one output the ELF for the image? Is it just the file of [image name] in ~/.ops/images ? Or is it the case that terraform should build a correctly pre-configured image as part of the apply process?w Always good to have other options, of course! I do appreciate the minimalism. This is exciting :) The terraform docs example uses GCP, perhaps if I figure out how to do it on AWS I could PR the docs with an example. At that stage where my questions lead to more questions.