Because the time string is provided by the event publisher, we
can't have nice things. They can choose whatever format they want,
it may not even be valid.
Before this project was going to be a buffalo plugin, it was going to be
our own rapid-devlopment code generator. At that point, it made sense to
generate code in support of many different HTTP frameworks. That
doesn't make any sense anymore, so I'm removing the code artifacts that
suggest that strategy.
Previously, `eventgrid.App` was a struct composed of a `buffalo.App`.
The idea being that one could have an eventgrid.App that exposed all of
the functionality seamlessly of a `buffalo.App`. However, in practice,
everybody will construct a `buffalo.App` first, because that's the
primary piece of functionality they're looking for. The process to build
an EventGrid app from a buffalo app was a huge pain. For that reason,
changing it so that one simply casts is a much easier way to consume it.
Commands added to:
- Deploy a dockerized application to Azure. (Presumably this uses AKS)
- Add an Action to a buffalo application specialized for handling
Event Grid events.
Fixes#2.