pawabase emulate runs the same validation and planning as a real deploy, but against a simulated environment stored in .pawabase/emulator-<env>.json. It never touches a server.

​
Why

  • Try it with no key. New to the tool, or a teammate without credentials.
  • See the plan the first time. The simulation starts empty, so you see everything as +, then edit and re-run to see changes as ~.
  • Catch ordering and reference problems before you ever deploy.
  • Fast tests in CI: emulate in a pull request without secrets.

​
What it is not

It’s a simulation of the plan, not a running Pawabase. It doesn’t run flows, check policies against real requests or create real tables. To test behaviour, deploy to a development environment and use Studio and your app.

​
Typical workflow

  1. pawabase validate
  2. pawabase emulate, read the output.
  3. Edit, pawabase emulate again.
  4. pawabase plan against a real development environment.
  5. pawabase deploy.
Commit .pawabase/ only if you want a shared simulation; usually add it to .gitignore.

Plan and deploy

The real thing.

Validate

The offline checks.