Zack Patrick

I propose we introduce a new entity, `application`, that encapsulates both a `service` and an application loadbalancer. The terraform design would look something like: ``` resource "layer0_application" "guestbook" { name...

*From Slack* * because of the nature of the retry, the "unable to assume role" error, for example, never gets returned to the outer `retry.Retry` * another issue is maybe...

RE: idea for a new entity, `application`, here: https://github.com/quintilesims/layer0/issues/110

I realize what I'm about to propose is a little radical, but I proposed this way back when we first created a ticket for using ALBs and it seems to...

this also applies to resources created by the layer0 api