# Upgrading to v0.11.0

> Upgrade Falak to v0.11.0 (config as code): control plane and agents, the new config.* permissions, API tokens, named workers, 308 redirects.

Source: https://falak.sh/docs/operations/upgrade-to-v0-11/

v0.11.0 adds [config as code](/docs/guides/config-as-code/): a project described in one `falak.yaml` in its repository. It is opt-in per project, so the upgrade itself changes little. Read the notes below before you run `falak-ctl update`.

## Update

1. Update the control plane:

   ```bash
   falak-ctl update --version v0.11.0
   ```

   The update runs the new migrations as usual.

2. Update every agent: **Servers → Update all agents** (see [Agent upgrades](/docs/servers/agent-upgrades/)).

3. Update the CLI on your machines if you want the new commands (`falak init`, `plan`, `apply`…). Older CLIs keep working for everything else. See [Install and log in](/docs/cli/install-and-login/).

## Permissions and API tokens

The new permissions `config.view`, `config.apply`, `config.approve` and `config.destroy` are given to the existing roles automatically when the update migrates; there is nothing to do for members.

| Permission | Roles (besides owner) |
|---|---|
| `config.view` | admin, developer, viewer |
| `config.apply` | admin, developer |
| `config.approve` | admin |
| `config.destroy` | admin |

A token created with a list of abilities doesn't get the new ones. Create a token with the `config.*` abilities the new CLI commands need. Tokens with every ability are fine.

## Nothing changes until a source is enabled

A project keeps working exactly as before until its config source is enabled (**Project settings → Config as code**, or `falak config source set`). For a new project, an admin lists the servers the project's file may place units on. See the [quick start](/docs/guides/config-as-code/#quick-start).

## Behaviour changes

- **Workers now have a name.** Workers made in the dashboard have none and export as `worker-<n>`; a file using that key adopts the worker and names it.
- **Dashboard edits of file-managed fields answer 422**, and managed services can't be renamed or deleted. Fields the file doesn't set stay editable; disabling the source makes everything editable again.
- **Former panel domains redirect with 308.** Domains kept with `falak-ctl domain set --keep-old` now redirect with `308`, so POSTs keep their method. See [Change the domain](/docs/operations/change-domain/).

## Checklist

| | |
|---|---|
| ☐ | `falak-ctl update --version v0.11.0` done |
| ☐ | Every agent updated |
| ☐ | API tokens with a list of abilities given the `config.*` abilities they need |
| ☐ | CLI updated where you use config as code |

## Next steps
