# `Wardrik.Deployment`

Operations on the deployment: listing its nodes and reloading every agent's definition.

    Wardrik.Deployment.nodes(scope)
    #=> {:ok, %Wardrik.Nodes{nodes: [%Wardrik.Node{name: "wardrik@box1", agents: 12}], asleep: 40}}

# `nodes`

```elixir
@spec nodes(Wardrik.Scope.t(), term()) :: term() | :ok | {:error, Wardrik.Error.t()}
```

List the deployment's nodes

`GET /v1/deployment/nodes`

# `reload`

```elixir
@spec reload(Wardrik.Scope.t(), term()) :: term() | :ok | {:error, Wardrik.Error.t()}
```

Read every agent's definition again

Each awake agent takes its definition as it reads now from its next turn, and each sleeping one as it wakes. With resources, only the agents the patterns cover are brought to theirs. The node that answers reads its declarations, servers and triggers again too.

`POST /v1/deployment/reload`

---

*Consult [api-reference.md](api-reference.md) for complete listing*
