abrown38andClaude Opus 5.5
2880f7ddc9
Changesets, as in Jarl: configuration changes are operations that can be staged in a changeset, checked as they are added (validation and nft -c), reviewed with the diff of the ruleset, and applied together as one history entry, then on probation like any change made over the network. The web UI collects edits for review by default (pending rows, a bar with Review and Apply now, a Changes page, a switch for live edits); hc stages with -C ID or HOUSECARL_CHANGESET (checked like JARL_CHANGESET) and has hc changeset create/list/show/diff/apply/discard/remove. Undo, import and takeover refuse a changeset. --dry-run shows the ruleset's diff. Bandwidth and quotas: rate limits in bytes, per source or destination; quotas per rule or per address that reset daily, weekly, monthly on a day, or by hand, with their usage carried across reloads, saved for reboots, shown by hc quotas and on the rules page, and reset with hc rule reset-quota. Rules that count traffic are checked before established connections are accepted (so they see every packet) and can't accept. Per-address limits group IPv6 by /64 by default (--group-v4/-v6). Per-source rate meters use update. The importer turns meters, byte rates and quotas into these fields. The examples in the web UI, hc's help and the docs use documentation addresses and generic names instead of the maintainer's network. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
57 lines
1.7 KiB
Go
57 lines
1.7 KiB
Go
package model
|
|
|
|
import (
|
|
"encoding/json"
|
|
"time"
|
|
)
|
|
|
|
// Changeset statuses.
|
|
const (
|
|
ChangesetOpen = "open"
|
|
ChangesetApplied = "applied"
|
|
ChangesetDiscarded = "discarded"
|
|
)
|
|
|
|
// Changeset is a list of changes, staged to be reviewed and applied
|
|
// together (or discarded). Applied, it is one history entry.
|
|
type Changeset struct {
|
|
ID int64 `json:"id"`
|
|
UserID int64 `json:"user_id,omitempty"`
|
|
Username string `json:"username"`
|
|
Via string `json:"via"`
|
|
Description string `json:"description"`
|
|
Status string `json:"status"`
|
|
Ops []Op `json:"ops"`
|
|
CreatedAt time.Time `json:"created_at"`
|
|
UpdatedAt time.Time `json:"updated_at"`
|
|
// HistoryID is the history entry an applied changeset became.
|
|
HistoryID int64 `json:"history_id,omitempty"`
|
|
}
|
|
|
|
// Operations.
|
|
const (
|
|
OpCreate = "create"
|
|
OpUpdate = "update"
|
|
OpDelete = "delete"
|
|
OpMove = "move"
|
|
OpSettings = "settings"
|
|
)
|
|
|
|
// Op is one change, as the API received it, so it can be stored and
|
|
// replayed on whatever the configuration is when it is applied.
|
|
type Op struct {
|
|
Seq int `json:"seq"`
|
|
Op string `json:"op"` // create, update, delete, move, settings
|
|
Kind string `json:"kind,omitempty"`
|
|
// Ref names the object (ID, or name) for update, delete and move.
|
|
Ref string `json:"ref,omitempty"`
|
|
// ID is the object a create makes, given when it is staged so later
|
|
// operations can name it.
|
|
ID int64 `json:"id,omitempty"`
|
|
// Data is the object (create), the fields to change (update,
|
|
// settings) or where to move it (move).
|
|
Data json.RawMessage `json:"data,omitempty"`
|
|
Summary string `json:"summary"`
|
|
AddedAt time.Time `json:"added_at"`
|
|
}
|