BREAKING CHANGE: In the upcoming 3.x Konnect Terraform provider, releasing at the end of August 2025, the provider deploys a v3 Dev Portal using the konnect_portal resource. If you are using Dev Portal v2 (classic), you need to migrate to the konnect_portal_classic resource in version 2.x of the Terraform provider before upgrading.
You can migrate your konnect_portal Terraform resource to the new konnect_portal_classic resource using import and removed blocks in the manifests or using the CLI. We recommend using the import/removed blocks in manifests.
Get your Dev Portal ID from the Terraform state:
terraform state show konnect_portal.my_portal | grep "id"
Copied!
You can also do this from the Konnect UI by navigating to Dev Portal in the sidebar, clicking the Classic tab, and clicking on your v2 Dev Portal.
Rename konnect_portal to konnect_portal_classic in your manifest. For example:
resource "konnect_portal_classic" "my_portal" { name = "My New Portal" auto_approve_applications = false auto_approve_developers = false is_public = false rbac_enabled = false}import { to = konnect_portal_classic.my_portal id = "854cb4ce-8a3f-4cf7-b878-52347a78d8d6"}removed { from = konnect_portal.my_portal lifecycle { destroy = false }}
Copied!
Warning: If the removed block is missing, the Dev Portal will be destroyed.
Apply all of the resource changes using Terraform:
terraform apply -auto-approve
Copied!
Remove the import and removed lines in your manifest.
Apply all of the resource changes using Terraform:
terraform apply -auto-approve
Copied!
Some things will say they need updating. It’s safe to do so as it’s just the state file updating IDs and references.
It’s not recommended, but you can edit your state file directly to migrate. To do this, search "type":"konnect_portal" and replace with "type": "konnect_portal_classic".