wintermeyer
Fetch a user by email address
Setup:
mix igniter.install ash_authentication_phoenix
mix ash_authentication.add_strategy password
I create a user in the web application. Now I want to access that user in the iex. How can I do that? This doesn’t work:
iex(5)> ExampleApp.Accounts.User |> Ash.Query.filter(email = "bob@example.com") |> Ash.read!()
** (Ash.Error.Invalid) Invalid Error
* No primary action of type :read for resource ExampleApp.Accounts.User, and no action specified
The resource includes this code:
read :get_by_email do
description "Looks up a user by their email"
get? true
argument :email, :ci_string do
allow_nil? false
end
filter expr(email == ^arg(:email))
end
How can I use that in the iex to fetch a single user by his email address?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Marked As Solved
zachdaniel
Oh, right
I forgot that we generated that action in the auth generators TBH 
I thought it was a custom action you had written.
You can use that existing action. In that case, the only thing you need is this:
Generally speaking, making an action just to get something by a given field is not necessary, because code interfaces have
get_byoption, and you can useAsh.getas well. However, in the case ofAshAuthenticationit needs to be guaranteed to have an action whose name it knows in order to look up users for authentication. You’re free to use that generated action for this as wellAlso Liked
zachdaniel
There are examples of using
Ash.getin the read actions guide:The most idiomatic way to do this is as follows:
Add the default read
Add a code interface on the domain
Call it
zachdaniel
Relevant docs on primary actions: Actions — ash v3.29.3
I considered making the generators add a primary read action, but users is a pretty sensitive resource and I wanted to add only the minimal required to power authentication.
You will also need to add
authorize?: falseto your call because of the policies on users. A mild inconvenience, but the security benefits are worth itSo after adding a primary action:
Ash.get!(User, <id>, authorize?: false)