diff --git a/website/docs/using-qovery/configuration/environment.md b/website/docs/using-qovery/configuration/environment.md
index 99a7ac77a9..d30c13ee61 100644
--- a/website/docs/using-qovery/configuration/environment.md
+++ b/website/docs/using-qovery/configuration/environment.md
@@ -1,5 +1,5 @@
---
-last_modified_on: "2023-06-14"
+last_modified_on: "2023-08-04"
title: "Environment"
description: "Learn how to configure your Environments on Qovery"
---
@@ -215,6 +215,24 @@ When cloning an environment, every configuration of the original environment wil
- [Application custom domains][docs.using-qovery.configuration.application#domains]: custom domains are not cloned to avoid collision.
- [Application BUILT_IN variables][docs.using-qovery.configuration.environment-variable#built_in-variables]: Since completely new services will be create, the original built_in variables will be replaced. Aliases and overrides are preserved during the clone operation.
+## Terraform exporter
+
+You can export the configuration of your environment as a Terraform manifest via the `Export as Terraform` option. This is helpful when you want to manage your configuration via Terraform: instead of creating the terraform manifest by hand, you can build the setup via the Qovery interface and export is as a Terraform file
+
+The export will contain the Terraform definition of the environment, the services within it but as well all the other resources linked to the environment (organization, cluster, project).
+
+You can decide wether or not the export should contain or not the secrets defined within the Qovery console.
+
+Here's a video explaining how it works:
+
+
+
+
## Deploy an environment
Have a look at the [Deployment Management][docs.using-qovery.deployment] section for more information on how to deploy your environment.
diff --git a/website/docs/using-qovery/configuration/environment.md.erb b/website/docs/using-qovery/configuration/environment.md.erb
index 5de8b86073..cd804be21f 100644
--- a/website/docs/using-qovery/configuration/environment.md.erb
+++ b/website/docs/using-qovery/configuration/environment.md.erb
@@ -206,6 +206,24 @@ When cloning an environment, every configuration of the original environment wil
- [Application custom domains][docs.using-qovery.configuration.application#domains]: custom domains are not cloned to avoid collision.
- [Application BUILT_IN variables][docs.using-qovery.configuration.environment-variable#built_in-variables]: Since completely new services will be create, the original built_in variables will be replaced. Aliases and overrides are preserved during the clone operation.
+## Terraform exporter
+
+You can export the configuration of your environment as a Terraform manifest via the `Export as Terraform` option. This is helpful when you want to manage your configuration via Terraform: instead of creating the terraform manifest by hand, you can build the setup via the Qovery interface and export is as a Terraform file
+
+The export will contain the Terraform definition of the environment, the services within it but as well all the other resources linked to the environment (organization, cluster, project).
+
+You can decide wether or not the export should contain or not the secrets defined within the Qovery console.
+
+Here's a video explaining how it works:
+
+
+
+
## Deploy an environment
Have a look at the [Deployment Management][docs.using-qovery.deployment] section for more information on how to deploy your environment.
diff --git a/website/docs/using-qovery/integration/terraform.md b/website/docs/using-qovery/integration/terraform.md
index fe6474fe37..badd716532 100644
--- a/website/docs/using-qovery/integration/terraform.md
+++ b/website/docs/using-qovery/integration/terraform.md
@@ -1,5 +1,5 @@
---
-last_modified_on: "2023-05-20"
+last_modified_on: "2023-08-04"
title: "Terraform"
description: "Learn how to use Terraform with Qovery"
---
@@ -23,18 +23,22 @@ Terraform can be used in 2 context:
## Deploy Qovery with Terraform
+Qovery integrates with Terraform to create a complete workflow with a strong developer and operations experience for the different teams from development to critical production applications. By integrating Terraform with Qovery, your team can quickly implement governance at scale while drastically improving the developer experience when deploying and managing applications.
+
Check out our Terraform Provider on [Terraform Registry](https://registry.terraform.io/providers/Qovery/qovery/latest/docs) and [GitHub](https://github.com/Qovery/terraform-provider-qovery).
-Qovery integrates with Terraform to create a complete workflow with a strong developer and operations experience for the different teams from development to critical production applications. By integrating Terraform with Qovery, your team can quickly implement governance at scale while drastically improving the developer experience when deploying and managing applications.
-
### Examples
Check out our Terraform examples [here](https://github.com/Qovery/terraform-examples).
+### Terraform Exporter
+
+Qovery allows you to export your environment as a Terraform Manifest. Check [the Terraform Exporter documentation][docs.using-qovery.configuration.environment#terraform-exporter] to know more.
+
### Resources
- [Qovery Terraform Registry](https://registry.terraform.io/providers/Qovery/qovery/latest/docs)
@@ -67,6 +71,7 @@ Check out our Terraform examples [here](https://github.com/Qovery/lifecycle-job-
Feel free to open a thread on our [Community Forum][urls.qovery_forum]. We will be happy to help you.
+[docs.using-qovery.configuration.environment#terraform-exporter]: /docs/using-qovery/configuration/environment/#terraform-exporter
[docs.using-qovery.configuration.lifecycle-job]: /docs/using-qovery/configuration/lifecycle-job/
[guides.tutorial.how-to-use-lifecycle-job-to-deploy-any-kind-of-resources]: /guides/tutorial/how-to-use-lifecycle-job-to-deploy-any-kind-of-resources/
[urls.qovery_forum]: https://discuss.qovery.com/
diff --git a/website/docs/using-qovery/integration/terraform.md.erb b/website/docs/using-qovery/integration/terraform.md.erb
index e09ef34dfd..d3a385f403 100644
--- a/website/docs/using-qovery/integration/terraform.md.erb
+++ b/website/docs/using-qovery/integration/terraform.md.erb
@@ -12,18 +12,22 @@ Terraform can be used in 2 context:
## Deploy Qovery with Terraform
+Qovery integrates with Terraform to create a complete workflow with a strong developer and operations experience for the different teams from development to critical production applications. By integrating Terraform with Qovery, your team can quickly implement governance at scale while drastically improving the developer experience when deploying and managing applications.
+
Check out our Terraform Provider on [Terraform Registry](https://registry.terraform.io/providers/Qovery/qovery/latest/docs) and [GitHub](https://github.com/Qovery/terraform-provider-qovery).
-Qovery integrates with Terraform to create a complete workflow with a strong developer and operations experience for the different teams from development to critical production applications. By integrating Terraform with Qovery, your team can quickly implement governance at scale while drastically improving the developer experience when deploying and managing applications.
-
### Examples
Check out our Terraform examples [here](https://github.com/Qovery/terraform-examples).
+### Terraform Exporter
+
+Qovery allows you to export your environment as a Terraform Manifest. Check [the Terraform Exporter documentation][docs.using-qovery.configuration.environment#terraform-exporter] to know more.
+
### Resources
- [Qovery Terraform Registry](https://registry.terraform.io/providers/Qovery/qovery/latest/docs)