We ended up choosing an approach where Dayron replaces the entire Ecto.Repo. A few points about that choice:
simplest solution, because we don't need queries support
we just need to allow sending params directly to the api request, such Repo.get(User, %{query_params})
a new repo does not need everything a DB Repo provides, like transactions, migrations, cli taks for bd management, connections, etc
we can use a custom Rest Model to work together with Ecto.Schema to define the struct, allow override callbacks to custom validate the api response before assigning to the stuct
our adapters are http clients, and we're going to start with HTTPoison
We ended up choosing an approach where Dayron replaces the entire Ecto.Repo. A few points about that choice:
hergem