CuraDevOps

tag: Hashicorp · 4 items

2026-08-28 · HashiCorp Blog · source ↗ #hashicorp#infrastructure#documentation
  • Platform/SRE — Learn: If your stack includes Vault, Consul, or Terraform, the refreshed HVDs are a useful reference for validated production deployment patterns — worth a bookmark, but no change to running infrastructure.
  • CI/CD — Skip
  • Leader — Skip
2026-08-27 · HashiCorp Blog · source ↗ #hashicorp#identity#scim
  • Platform/SRE — Plan: If your org uses HCP (Vault, Terraform Cloud, etc.) and an external IdP, evaluate enabling SCIM provisioning to automate user/group sync and reduce manual access management overhead; no deadline, but worth scheduling this quarter.
  • CI/CD — Skip
  • Leader — Plan: SCIM provisioning on HCP reduces IAM admin overhead and improves access consistency across HCP services — worth adding to your identity governance standards review if the org is standardized on HashiCorp HCP.
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.
2026-07-10 · HN (terraform) · source ↗ #terraform-cdk#iac#hashicorp
  • Platform/SRE — Learn: Teams using CDKTF for IaC should read this discussion to gauge whether HashiCorp/IBM intends to maintain it long-term; no deprecation date in signals, so no action required now.
  • CI/CD — Skip
  • Leader — Plan: Against the backdrop of HashiCorp’s BSL relicensing and IBM acquisition, a high-signal HN discussion on CDKTF’s direction is a prompt to evaluate whether to continue standardizing on CDKTF or assess alternatives like OpenTofu CDK this planning cycle.