CuraDevOps

tag: Vendor-Risk · 5 items

Plan Terraform Registry Terms of Service updated, restricting usage
2026-10-23 · HN (terraform) · source ↗ #terraform#iac#vendor-risk
  • Platform/SRE — Plan: Platform teams pulling providers and modules from the public Terraform Registry are subject to the revised ToS; review the updated terms and evaluate whether to implement a provider network mirror or private registry to ensure automated and commercial usage remains compliant.
  • CI/CD — Plan: CI pipelines that run terraform init against the public registry are exposed to ToS restrictions on automated usage; audit pipeline patterns and consider mirroring providers or switching to the OpenTofu registry to keep builds compliant.
  • Leader — Plan: This ToS change compounds the earlier BSL relicensing as a vendor-risk signal for orgs standardized on Terraform; use this moment to formally evaluate OpenTofu as the org’s IaC standard and assess whether current Registry usage complies with the new terms before the next planning cycle.
Learn HashiCorp CEO describes Terraform community building as "Malicious"
2026-10-23 · HN (terraform) · source ↗ #terraform#hashicorp#vendor-risk
  • Platform/SRE — Learn: Adds cultural context to the ongoing HashiCorp–community tension following the BSL relicensing; no new concrete deadline or action, but relevant background for teams weighing Terraform vs. OpenTofu.
  • CI/CD — Skip
  • Leader — Learn: Shapes thinking on long-term HashiCorp vendor risk—the CEO’s framing of community engagement informs the strategic conversation around staying on HashiCorp Terraform versus migrating to OpenTofu, but no new contract or licensing fact is introduced here.
Learn What has Docker become? A community retrospective
2026-10-21 · HN (docker) · source ↗ #docker#vendor-risk#platform-engineering
  • Platform/SRE — Learn: Offers perspective on Docker’s product evolution and ecosystem fragmentation — useful context when evaluating container toolchain choices, but no operational change required.
  • CI/CD — Skip
  • Leader — Learn: Community retrospective on Docker’s strategic direction and vendor positioning; worth reading when assessing long-term container toolchain vendor risk or build-vs-buy decisions.
Plan archived Terraform Registry Terms of Service Updated
2026-07-22 · HN (terraform) · source ↗ #terraform#licensing#vendor-risk
  • Platform/SRE — Plan: The updated ToS may restrict how the Terraform Registry can be consumed, particularly by tooling or automation that competes with or mirrors registry content. Review current Terraform and provider-download patterns against the new terms and evaluate whether a migration to OpenTofu or a self-hosted registry should be scoped this quarter.
  • CI/CD — Learn: Pipelines that pull Terraform providers and modules via the public registry could be indirectly affected if the new ToS introduces usage restrictions on automated clients; worth monitoring, but no concrete pipeline action is required yet.
  • Leader — Plan: A ToS change on a registry that most Terraform-standardized orgs depend on is a direct vendor-risk signal; evaluate whether current registry consumption falls under any newly restricted terms and assess OpenTofu as a contingency before any enforcement timeline is announced.
Learn archived HashiCorp CEO labels Terraform community-building efforts 'Malicious'
2026-07-22 · HN (terraform) · source ↗ #terraform#hashicorp#vendor-risk
  • Platform/SRE — Skip
  • CI/CD — Skip
  • Leader — Learn: The CEO’s characterization of community engagement as adversarial adds cultural context to HashiCorp’s posture following the BSL relicensing — useful background when evaluating long-term vendor risk or the case for OpenTofu migration, but no new fact or deadline changes the decision calculus today.