<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Terraform-Cdk on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/terraform-cdk/</link><description>Recent content in Terraform-Cdk on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jul 2026 11:00:57 -0500</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/terraform-cdk/index.xml" rel="self" type="application/rss+xml"/><item><title>Terraform CDK future direction discussed on HN</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-the-future-of-terraform-cdk/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-the-future-of-terraform-cdk/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> 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.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Against the backdrop of HashiCorp&amp;rsquo;s BSL relicensing and IBM acquisition, a high-signal HN discussion on CDKTF&amp;rsquo;s direction is a prompt to evaluate whether to continue standardizing on CDKTF or assess alternatives like OpenTofu CDK this planning cycle.&lt;/li>
&lt;/ul></description></item></channel></rss>