$ the-wire · showcase
Consul security scans fail on any CVE, vagrant-registry-export ships v0.1.0
By RepoJournal · Filed · About HashiCorp · Composed from the cited sources · methodology
Consul and consul-dataplane now fail their security scan workflows whenever a CVE is detected, and the Vagrant registry exporter cut its first release at v0.1.0.
update security scan workflow hashicorp/consul
Consul's security scanner workflow now uses security-scan.hcl so suppressed vulnerabilities are honored, lists detected CVEs in a readable format, and fails the run if any CVE is found. Expect red checks on PRs that previously passed with known findings that are not recorded as suppressions in that config.
Update security scanner workflow hashicorp/consul-dataplane
consul-dataplane's workflow got the same three changes: fail on any detected CVE, honor suppressed vulnerabilities via security-scan.hcl, and print CVEs readably. Any advisory suppressed outside that config file will now surface as a build failure rather than a silent pass.
v0.1.0 hashicorp/vagrant-registry-export
The exporter reached v0.1.0 with its initial implementation plus internal configuration and CI workflows, dependabot scheduling and test triggers; separate work updated the version tag for the release. It is a first cut, so treat the API as unsettled.
Transit: Remove enterprise banner notes for key types, `type` param is entirely enterprise for import_version (#3782) hashicorp/web-unified-docs
The docs no longer flag individual transit key types as enterprise-only, because the type parameter as a whole is enterprise-gated for import_version. Readers following BYOK guidance get one gating rule instead of per-type banners.
Vault: Agentic IAM Auth0 edits hashicorp/web-unified-docs
Auth0 setup docs for Vault's agentic IAM path were revised from developer feedback: a note that enterprise Auth0 requires a licence, PAR requests enabled in the application, unneeded PAR and authorization details removed, and updated management API and baseline token steps. A companion commit carries the same edits, and TFE 2.1.0 docs were updated with the GA date and the working release notes ...
