Florent Jaby

@stendarr HTTP Spec Jokes are serious business ಠ_ಠ

@akofman Out of curiosity, how did you make it work ?

Well, this PR passes all tests that the master branch passes ! :D

/wizz @clarkie

I would love this.

My use-case involves creating temporary environments for each pull request. Ideally I'd have a build triggered to clean these up. Waiting for merge on master doesn't give me as much...

For anyone interested, my current workaround is this ```hcl resource "heroku_addon" "database" { for_each = toset([var.db_plan]) app = heroku_app.api.name plan = "heroku-postgresql:${each.key}" } ```

thanks for your reply ! I didn't know if this sort of information was available through the API so I added the 2nd proposition just in case.

I support this because I had to inline my ascii schematics inside a block for it to render properly

I've got a pull request hanging fixing this. https://github.com/Floby/TermKit/commit/69967de48a27c1f87e7b9bf73ff4cbd1ffbe7b3c https://github.com/unconed/TermKit/pull/6