AshAuthentication with non-Postgres Data Layers?
I am writing a small "microservice" which takes a JSON post from an internal system and does a side effect (i.e. validates it, processes it based on if CAD drawings in a directory exist or not, then leaves a custom CSV in a directory being watched by vendor software). I have it working without Ash (just using OpenAPISpex and phx gen.auth api keys) but I need to rewrite it so the release will run as a Windows Service for performance reasons (don't ask!! 
) and thought this would be a great very easy way to start learning some Ash resources, actions, and json_api at least on a simple easy project!
The API and side effect generating stuff works great (simple/embedded data layer) I just need to add api key authentication so I added AshAuthentication. Looking at the code it seems agnostic to the data layer but every example online all assumes AshPostgres and this may be the only way to get it to work. This service is not publicly-accessible and of course HTTPS is used but I still want some sort of key to be checked even if the hash is stored in an env var and read by runtime config then checked. Or in SQLite data layer or a JSON/CSV file or something. I just don't want to add the complexity of adding PGSQL on Windows to this simple deployment.
) and thought this would be a great very easy way to start learning some Ash resources, actions, and json_api at least on a simple easy project!The API and side effect generating stuff works great (simple/embedded data layer) I just need to add api key authentication so I added AshAuthentication. Looking at the code it seems agnostic to the data layer but every example online all assumes AshPostgres and this may be the only way to get it to work. This service is not publicly-accessible and of course HTTPS is used but I still want some sort of key to be checked even if the hash is stored in an env var and read by runtime config then checked. Or in SQLite data layer or a JSON/CSV file or something. I just don't want to add the complexity of adding PGSQL on Windows to this simple deployment.
