From b0dc02509ba20c90ca134b3ce1cae63d529c8c91 Mon Sep 17 00:00:00 2001 From: Livio Spring Date: Thu, 27 Jul 2023 10:01:36 +0200 Subject: [PATCH] docs: fix formatting of idp migration (#6279) --- docs/docs/guides/integrate/identity-providers/migrate.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/docs/guides/integrate/identity-providers/migrate.mdx b/docs/docs/guides/integrate/identity-providers/migrate.mdx index 497fae6b9f..b7564a9745 100644 --- a/docs/docs/guides/integrate/identity-providers/migrate.mdx +++ b/docs/docs/guides/integrate/identity-providers/migrate.mdx @@ -33,7 +33,9 @@ To migrate to a specific provider, you need to follow a few essential steps: # terraform state rm *address* terraform state rm zitadel_idp_oidc.oidc_idp ``` -After this command you can also remove the resource from the terraform files, as it is not managed anymore but also not deleted + +After this command you can also remove the resource from the terraform files, as it is not managed anymore but also not deleted. + 3. Make the corresponding API call to [migrate the IDP](./migrate#migrate-generic-oidc-provider), save the ID of the IDP for the import 4. Before applying the Terraform resources again, import the new IDP resource. ```bash @@ -52,4 +54,4 @@ After this command you can also remove the resource from the terraform files, as terraform import zitadel_idp_google.google 222302827723096428:GOCSPX-***** ``` -You have now migrated your provider and you should be able to apply the resource again. There should be no changes and the IDP is maintained by Terraform again. \ No newline at end of file +You have now migrated your provider and you should be able to apply the resource again. There should be no changes and the IDP is maintained by Terraform again.