Version history
Every Apply is recorded as a commit. You can scroll back through your infrastructure’s history and load any past state onto the canvas.
A commit is only written at Execute time. Edits and Plans are not recorded. The history is a faithful record of what actually hit your provider, not of every intermediate edit you tried. See Reconciliation for why.
The history panel
Section titled “The history panel”Open the history panel from the dock tabs. It lists commits newest first, with:
- The commit message.
- The author.
- The timestamp.
- An outcome badge: applied, partial, failed, or aborted.
The outcome reflects how the Apply for that commit actually went, computed from the per-operation results.
Browse a past state
Section titled “Browse a past state”Select a commit to inspect it. You can see the desired state the commit captured and the plan that was run. This is read-only. Browsing a past state does not change your canvas.
Roll back
Section titled “Roll back”Checkout a past commit to load its desired state onto the canvas. CrossXCloud replaces the canvas with that snapshot so you can edit from there.
Checkout is just a canvas operation. It does not touch your live infrastructure until you Plan and Apply again. To roll back your real resources to a past state, checkout the commit, then open Plan and review the diff that returns you to that state, then Apply.
Where history lives
Section titled “Where history lives”History is stored as records keyed by your project, alongside the rest of your project data. Every commit also keeps the “latest snapshot” of your desired state in sync, which is what the read-only canvas in CrossXWeb reads.
- Plan and Apply for what gets recorded.
- Reconciliation for the commit-on-execute model.
- Organizations and projects for where projects come from.