You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/migration_guide_v2.md
+5-8Lines changed: 5 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,7 @@ description: |-
4
4
Migrating your Scaleway provider from v1 to v2.
5
5
---
6
6
7
-
# Migrating from v1 to v2
8
-
9
-
-> **Note:** The version 2 is not released yet but versions `v1.11+` allow you to do a smooth migration to the `v2`.
10
-
In other words, there will be no breaking change between `v1.11+` and `v2`.
11
-
The `v2` roadmap is available [here](https://github.com/scaleway/terraform-provider-scaleway/issues/125).
7
+
# Migrating from Scaleway provider v1 to v2
12
8
13
9
This page guides you through the process of migrating your version 1 resources to their version 2 equivalent.
14
10
To prepare the launch of all new Scaleway products, we completely changed the naming of all resources (as well as their attributes) in version 2 of the Terraform provider.
@@ -17,9 +13,10 @@ To prepare the launch of all new Scaleway products, we completely changed the na
17
13
18
14
### Version configuration
19
15
20
-
-> **Note:** Before upgrading to `v2+`, it is recommended to upgrade to the most recent `1.X` version of the provider (`v1.11.0`) and ensure that your environment successfully runs [`terraform plan`](https://www.terraform.io/docs/commands/plan.html) without unexpected change or deprecation notice.
16
+
-> **Note:** Before upgrading to `v2+`, it is recommended to upgrade to the most recent `1.X` version of the provider (`v1.17.2`) and ensure that your environment successfully runs [`terraform plan`](https://www.terraform.io/docs/commands/plan.html) without unexpected change or deprecation notice.
21
17
22
-
It is recommended to use [version constraints when configuring Terraform providers](https://www.terraform.io/docs/configuration/providers.html#version-provider-versions). If you are following these recommendation, update the version constraints in your Terraform configuration and run [`terraform init`](https://www.terraform.io/docs/commands/init.html) to download the new version.
18
+
It is recommended to use [version constraints when configuring Terraform providers](https://www.terraform.io/docs/configuration/providers.html#version-provider-versions).
19
+
If you are following these recommendations, update the version constraints in your Terraform configuration and run [`terraform init`](https://www.terraform.io/docs/commands/init.html) to download the new version.
23
20
24
21
Update to latest `1.X` version:
25
22
@@ -73,7 +70,7 @@ Below you find an overview of the changes in environment variables:
73
70
This should be your access key (e.g. `SCWZFD9BPQ4TZ14SM1YS`).
74
71
Your secret key (previously known as _token_) must be set in `SCW_SECRET_KEY` (`xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`).
75
72
76
-
Terraform can also read standard Scaleway configuration files.
73
+
Terraform can also read standard [Scaleway configuration files](https://github.com/scaleway/scaleway-sdk-go/blob/master/scw/README.md).
77
74
By doing so, you can use the same configuration between different tools such as the [CLI](https://github.com/scaleway/scaleway-cli) or [Packer](https://www.packer.io/docs/builders/scaleway).
0 commit comments