Tiernan

I've had a bit more of a think about it and have come to the conclusion Transactions aren't really feasible, but rows should work. I'm thinking for compatibility default behaviour...

I could see this being a resource that takes in the node id (either read out of the started VM, or by provisioning in the node ID into the VM...

> For example, what would it mean to delete this resource? We can't really "undo" a node drain so the resource would kind of just hang there? Marking as eligible...

> > Marking as eligible and ineligible for scheduling is a reversible operation > > That's a [different endpoint](https://www.nomadproject.io/api-docs/nodes#toggle-node-eligibility), so probably another resource altogether 🙂 > > So `nomad_node_drain` would...

> How does this sounds? Is it similar to what you had in mind? Yup that's exactly it. I like your idea of using the node metadata to filter on...

> There's a standard way to handle timeouts in Terraform: https://www.terraform.io/docs/extend/resources/retries-and-customizable-timeouts.html > > So it's mostly a matter of making sure that `Timeouts` is set in the resource schema and...

That explains the difference in behaviour. Is the type of the parameters required when the query is prepared, or when it is executed? Looking at the perl module they default...

Just ran into this on Vault 1.7.2, definitely still an issue.

> Hey aren't these typically OS / platform level concerns? Yes, but the specific behaviour I'm expecting here is when Vault attempts to write to the audit log, encounters an...

Personally the usecase I think this would be most helpful for is just to save on amount of config needed. Assuming your Nomad operators are trusted, the code running in...