Skip to content

doc: use project id instead or organization id in migration guide #767

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 12, 2021
Merged

doc: use project id instead or organization id in migration guide #767

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
96a9dc5
doc: use project id instead or organization id in migration guide
remyleone Jan 20, 2021
256ab05
Merge branch 'master' into fix_org_doc
remyleone Feb 12, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions docs/guides/migration_guide_v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,24 +59,25 @@ In order to unify configuration management across all scaleway developer tools,
Below you find an overview of changes in the provider config:

| Old provider attribute | New provider attribute |
| --------------------- | --------------------- |
| `access_key` | `access_key` |
| `token` | `secret_key` |
| `organization` | `organization_id` |
| --------------------- | ----------------------- |
| `access_key` | `access_key` |
| `token` | `secret_key` |
| `organization` | `project_id` |

~> **Important:** `access_key` should now only be used for your access key (e.g. `SCWZFD9BPQ4TZ14SM1YS`).
Your secret key (previously known as _token_) must be set in `secret_key` (`xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`).
You can use the value of your `organization_id` as your default `project_id` if you have not yet created a non default project.

Below you find an overview of the changes in environment variables:

| Old env variable | New env variable |
| ----------------------- | ------------------------------------------- |
| `SCALEWAY_ACCESS_KEY` | `SCW_ACCESS_KEY` |
| `SCALEWAY_TOKEN` | `SCW_SECRET_KEY` |
| `SCALEWAY_ORGANIZATION` | `SCW_DEFAULT_ORGANIZATION_ID` |
| `SCALEWAY_ORGANIZATION` | `SCW_DEFAULT_PROJECT_ID` |
| `SCALEWAY_REGION` | `SCW_DEFAULT_REGION` and `SCW_DEFAULT_ZONE` |
| `SCW_TLSVERIFY` | `SCW_INSECURE` |
| `SCW_ORGANIZATION` | `SCW_DEFAULT_ORGANIZATION_ID` |
| `SCW_ORGANIZATION` | `SCW_DEFAULT_PROJECT_ID` |
| `SCW_REGION` | `SCW_DEFAULT_REGION` |
| `SCW_TOKEN` | `SCW_SECRET_KEY` |

Expand Down Expand Up @@ -266,7 +267,7 @@ For more information check the [new volume `scaleway_instance_volume` resource](

`scaleway_ssh_key` was renamed to `scaleway_account_ssk_key`
The `key` attribute has been renamed to `public_key`.
A `name` required attribute and an `organization_id` optional attribute have been added.
A `name` required attribute and a `project_id` optional attribute have been added.

##### Removed: `scaleway_user_data`

Expand Down