Closed thebentern closed 5 years ago
It was giving me an Uninitialized constant on that previous AWS error. I'm sure we can come up with an alternative solution if that is preferable.
On Dec 15, 2016 5:46 PM, "Logan Serman" notifications@github.com wrote:
What was the problem this solved? Are you getting more AWS errors or is something wrong w/ the logic in the gem?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lserman/capistrano-elbas/pull/18#issuecomment-267478251, or mute the thread https://github.com/notifications/unsubscribe-auth/AIlWhNhvJJxNH0mIHlK5LQ12VT2sj03Vks5rIdFcgaJpZM4LOZBk .
Tracked in #34 , see my comments on #19.
What was the problem this solved? Are you getting more AWS errors or is something wrong w/ the logic in the gem?