3 ms·
> dependencies like databases being provisioned through static analysis in real-time. I'm probably extremely biased (I'm a sysadmin), but this feels like a ter
by yjftsjthsd-h 5y ago
> dependencies like databases being provisioned through static analysis in real-time.
I'm probably extremely biased (I'm a sysadmin), but this feels like a terrifying way to make your infrastructure entirely implicit and remove anybody's ability to coherently reason about the stuff underneath your application.
- inferiorhuman 5y agoOps monkey here: agreed. I'm not entirely averse to magic infrastructure beans but having an intermediate step where things are explicitly spelled out would make me far less nervous. Using shuttle to spit out a TF file – cool, using shuttle to automagically spin stuff up – terrifying.
- notreallyserio 5y agoIt seems like it'd be all too easy to accidentally create databases and then forget about them when you correct an annotation typo or something. I'm 100% sure that I would do that.
- yjftsjthsd-h 5y agoOr, if they try to solve that, you always have the much more exciting possibility of just deleting databases when you accidentally stopped referencing them for one commit:)
- lgas 5y agoThere are, of course, a range of other possibilities, such as sending an email when the last reference to a database is removed so that a human can intervene appropriately or having a web app that provides access to the current list of unreferenced databases.
- ur-whale 5y ago> but this feels like a terrifying way to make your infrastructure entirely implicit This exact problem is my main beef with an unfortunately common and popular style of functional programming : stuff so condensed, so abstracted and so focused on describing the problem all the while hiding the actual execution / implementation / solution layers it's quasi-impossible to reason about and understand what actually happens when the program runs.
- amboo7 5y agoYou can add tons of structured logs, log runtime configuration... as opposed to trying to "observe" what is going by collecting unrelated pieces of informal logs (the state of the art). People code at high level, tools write instrumented low-level code.
- codeisawesome 5y agoScarier to imagine a bug in the static analysis code :)
- openquery 5y agoHey! I'm one of the maintainers of the project so I thought I would address some of the comments here :) > this feels like a terrifying way to make your infrastructure entirely implicit and remove anybody's ability to coherently reason about the stuff underneath your application. There's two parts to this. The first is understanding what is happening under the hood since we're automatically provisioning so much for you (subdomain, LBs, DBs, etc.). Right now this is a little opaque, but a dashboard is in the roadmap to give users visibility on what's happening 'under the hood' - showing your provisioned infrastructure as well as how it's all wired up. The second point is about potentially destructive actions - here we're going to be following a 'terraformesque' philosophy where infrastructure diffs are presented to the user and need to be accepted explicitly when deploying (or via a `--auto-approve` flag).
- yjftsjthsd-h 5y agoI'm glad that it's in your sights. And yeah, a terraform style model where you generate an explicit plan and then separately apply it helps with both problems.