Skip to content

entrepot_waiver

A vulnerability waiver: findings matching it are ignored when deciding whether to quarantine a component. Repositories and components are matched with globs. Expired waivers stay defined (and in state) but no longer apply.

# Accept one vulnerability in one component until the upgrade lands.
resource "entrepot_waiver" "xz" {
vuln_id = "CVE-2024-3094"
component_pattern = "xz-utils@5.6.*"
reason = "Not shipped in production images; tracked in SEC-123"
expires_at = "2026-12-31T23:59:59Z"
}
# Ignore every finding in sandbox repositories.
resource "entrepot_waiver" "sandbox" {
vuln_id = "*"
repository_pattern = "sandbox-*"
reason = "Experimental repositories are not scanned for policy"
}
  • vuln_id (String) Vulnerability ID, e.g. CVE-2024-3094 or GHSA-…, or * for any vulnerability (then a repository or component pattern is required).
  • component_pattern (String) Glob over name or name@version of components, e.g. lodash@4.17.*. Default *.
  • expires_at (String) When the waiver stops applying, as an RFC 3339 timestamp (e.g. 2026-12-31T23:59:59Z). Unset: never expires.
  • reason (String) Why the finding is accepted (shown in the UI and audit log).
  • repository_pattern (String) Glob over repository names. Default *.
  • created_at (String) Creation time (RFC 3339, UTC).
  • created_by (String) Principal that created the waiver.
  • id (String) Server-assigned waiver ID (used for import).

The terraform import command can be used, for example:

Terminal window
# Waivers are imported by their server-assigned ID.
terraform import entrepot_waiver.xz 3f0c2a8e-6b1d-4f7a-9c55-2d8e1b7a4c90

Resource documentation generated from the provider’s schema (docs/resources/waiver.md in terraform-provider-entrepot).