Skip to main content
formae periodically checks the resources it knows about against the cloud and updates its inventory with observed changes. The inventory reflects the latest successful observation; it can lag a change until the next synchronization.

​
How synchronization works

Synchronization is enabled by default (every 5 minutes). On each run, formae reads the current state of every resource it knows about, managed and unmanaged alike, and compares it against what’s recorded. If something changed outside formae, through the cloud console, another IaC tool, or a script, formae updates its inventory when it observes the change. This does not automatically accept the change as desired intent. Synchronization does not edit Pkl or change cloud resources. On the next soft reconcile, review out-of-band changes that need a decision and choose whether to absorb or revert them. Absorption is recorded centrally as a reconcile, so a codebase is optional. If you maintain one, the assistant updates the selected project afterward; the CLI prints the queries and deletions needed to catch it up. --force retains its role of overwriting out-of-band changes with declared desired state. Synchronization is what lets you:
  • Use formae alongside other tools without conflicts
  • Make emergency changes through the cloud console when you need to
  • Collaborate with teammates using different workflows
  • Always have an accurate view of your infrastructure, regardless of how it was last touched

​
Configuration

Synchronization is on by default. Tune the interval, or turn it off, in your agent configuration:

​
Use cases

  • Emergency fixes. Make a quick change through the cloud console during an incident. formae picks it up on the next sync, so your recorded state stays current even if your forma code hasn’t changed yet.
  • Multi-tool environments. If your team uses more than one tool to manage infrastructure, synchronization keeps formae’s view accurate regardless of what made the change.
  • Gradual adoption. Keep using your existing tools while formae tracks everything in the background, building a complete, current view of your infrastructure as you migrate.
Synchronization works hand in hand with discovery. Discovery finds resources formae doesn’t know about yet; synchronization keeps everything formae already knows about current.

​
See also

  • Discovery: how formae finds resources it doesn’t manage yet.
  • Apply modes: soft vs. hard reconcile, and how out-of-band changes affect an apply.