Skip to content

Commit

Permalink
feat: added terraform exporter
Browse files Browse the repository at this point in the history
  • Loading branch information
acarranoqovery authored and evoxmusic committed Aug 4, 2023
1 parent 0b5525a commit 7ec8af9
Show file tree
Hide file tree
Showing 4 changed files with 51 additions and 6 deletions.
20 changes: 19 additions & 1 deletion website/docs/using-qovery/configuration/environment.md
Original file line number Diff line number Diff line change
@@ -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"
---
Expand Down Expand Up @@ -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:

<div class="video-container">
<p align="center">
<iframe src="https://www.loom.com/share/4642112b9f2846789fb0ba8fc14726b5" width="100%" height="100%" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen>
</iframe>
</p>
</div>


## Deploy an environment
Have a look at the [Deployment Management][docs.using-qovery.deployment] section for more information on how to deploy your environment.

Expand Down
18 changes: 18 additions & 0 deletions website/docs/using-qovery/configuration/environment.md.erb
Original file line number Diff line number Diff line change
Expand Up @@ -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:

<div class="video-container">
<p align="center">
<iframe src="https://www.loom.com/share/4642112b9f2846789fb0ba8fc14726b5" width="100%" height="100%" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen>
</iframe>
</p>
</div>


## Deploy an environment
Have a look at the [Deployment Management][docs.using-qovery.deployment] section for more information on how to deploy your environment.

Expand Down
11 changes: 8 additions & 3 deletions website/docs/using-qovery/integration/terraform.md
Original file line number Diff line number Diff line change
@@ -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"
---
Expand All @@ -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.

<Alert type="info">

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).

</Alert>

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)
Expand Down Expand Up @@ -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/
8 changes: 6 additions & 2 deletions website/docs/using-qovery/integration/terraform.md.erb
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<Alert type="info">

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).

</Alert>

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)
Expand Down

0 comments on commit 7ec8af9

Please sign in to comment.