Infrastructure as code

pip install pawabase-iac

pawabase init          # pawabase.toml, infra/app.py, .env.example
pawabase validate      # offline: every definition and every reference between them
pawabase emulate       # a pretend deploy: nothing real is touched, no key needed
pawabase plan          # what a deploy would change in the real environment (reads only)
pawabase deploy        # apply it; needs a deploy API key

​

Why use it

• Everything is code. Definitions are Python objects you can import, share and test.
• Checked before it is sent. Names, field types, constraints, policy conditions, flow graphs, template syntax, block settings and the references between all of them are validated on your machine, before anything is sent.
• A plan before a change. plan and deploy --dry-run show what would be created (+), changed (~, with the fields that differ) or removed (-).
• Safe by default. Pushing needs a secret API key; merge mode never deletes what your code doesn’t mention; production asks first; secrets never sit in the code.

​

What you can define

​

How it fits together

1. Validate checks everything offline.
2. Emulate rehearses a deploy against a simulated environment kept in a file. No server, no key.
3. Plan compares your code with the real environment and prints the differences.
4. Deploy applies them in dependency order.

​

Learn it in this order