Skip to content

v0.2.0 — experimental trusted-rule management

Choose a tag to compare

@Scriptception Scriptception released this 09 Sep 05:35
· 9 commits to main since this release
e017b2f

v0.2.0 — experimental trusted-rule management

Adds algosec_trusted_rule for a single A33.20 device/rule assignment, with comment, optional expiry, import, refresh/drift detection, deletion and replacement-only metadata changes. Enable it explicitly with experimental_trusted_rules = true; it is disabled by default and provider read-only mode remains the default.

  • Surface: 3 resources, 12 data sources, 20 implemented method/route operations. This is a managed-resource milestone, not complete AlgoSec product coverage.
  • Typed GET/POST/DELETE contracts, operation-specific acknowledgements, no write retries, conservative absence checks and recoverable owned state.
  • Rejects known invalid replacement expiry during planning before deleting the prior assignment. Unknown expiry and plan-to-apply date rollover remain apply-time limitations.
  • Existing A33.20 device groups remain separately gated by experimental_device_groups = true; the vendor marks group APIs Early Availability and does not recommend production use.
  • No existing resource or data-source schema is removed; dependencies are unchanged.

Verification and limitations

Release gates exercise race-enabled unit/Framework/Terraform protocol tests against synthetic local HTTPS fixtures, generated documentation parity, coverage mapping, vulnerability checks, package installation and schema validation. These do not establish live appliance compatibility. No live AlgoSec appliance acceptance or appliance mutations were performed for this release. A32.60 remains the base contract; trusted rules and groups use qualified A33.20 contracts. Read the trusted-rule contract, API coverage and live-acceptance checklist before enabling mutations.

Eight OS/architecture ZIPs are built for Linux, Windows, macOS and FreeBSD, amd64 and arm64. Runtime installation smoke is Linux amd64 only. Checksums and protocol manifest are signed with the existing shared Terraform key BB831B4CD32200DD15EDF4E9AB71E7968334DF52.

The v0.1.3 and v0.1.4 releases remain immutable.