AshLua exposes Ash actions to Lua scripts evaluated through the lua Elixir package, ensuring a consistent actor / tenant / context are propagated into every Ash call.

The Lua surface is resolved from Ash.Info.Manifest.generate/1 plus AshLua DSL. Domains with no explicit lua do namespace ... end config keep the legacy <domain>.<resource>.<action> callable shape; domains with explicit namespaces expose only their configured public action paths.

Example

defmodule MyApp.Accounts do
  use Ash.Domain, otp_app: :my_app, extensions: [AshLua.Domain]

  resources do
    resource MyApp.Accounts.User
  end
end

defmodule MyApp.Accounts.User do
  use Ash.Resource,
    domain: MyApp.Accounts,
    extensions: [AshLua.Resource]

  # ... attributes / actions ...
end

AshLua.eval!("""
  local user, err = accounts.user.create({ input = { name = "Zach" } })
  assert(err == nil)
  return user.id
""", otp_app: :my_app, actor: current_user)

Action callables always return (result, nil) on success and (nil, err_table) on failure. Wrap a call in Lua's built-in assert() for raise semantics:

local user = assert(accounts.user.create({ input = { name = "Zach" } }))

Actor / tenant / context

All three are host-supplied via the eval opts and are never reflected to or mutable from the script — there is no way for a Lua script to read or change the actor, tenant, or context.