From 10c4625ec6c36cd94d6ba4f1ba08f50f04f06ebf Mon Sep 17 00:00:00 2001 From: Stacey Salamon Date: Thu, 30 May 2024 16:34:55 +0200 Subject: [PATCH 1/6] update: teams migration guides deprecation info --- .../howto/create-manage-teams.md | 52 +++--- .../howto/migrate-from-teams-to-groups.md | 157 +++++++++++++++++- 2 files changed, 184 insertions(+), 25 deletions(-) diff --git a/docs/tools/aiven-console/howto/create-manage-teams.md b/docs/tools/aiven-console/howto/create-manage-teams.md index 9782d9fc..6286d037 100644 --- a/docs/tools/aiven-console/howto/create-manage-teams.md +++ b/docs/tools/aiven-console/howto/create-manage-teams.md @@ -2,32 +2,43 @@ title: Create and manage teams --- -**Teams** let you create user groups and assign different access levels to specific projects. +import ConsoleLabel from "@site/src/components/ConsoleIcons" -Users must be part of an organization before being added to a team. To create and manage -teams, click **Admin** and select **Teams**. +Teams are groups of users that you can assign to projects. -The members of the Account Owners team are automatically made super admin. Adding other -users to this team makes them a super admin with full access to your organization, -its units, and projects. Likewise, when you make a user a super admin, they are added -to the account owners team. +:::important[Teams have been deprecated and are being migrated to groups] -:::important -**Teams are becoming groups** +- **On DATE Z the Account Owners team will be removed.** -Groups are an easier way to control access to your organization's -projects and services for a group of users. -[Migrate your teams to groups](#migrate_teams_to_groups). + The Account Owners and super admin + are synced, so the removal of the Account Owners team will have no impact on your + operations. [Super admin](/docs/platform/concepts/orgs-units-projects#users-and-roles) + have full access to organizations. + +- **From DATE X you won’t be able to create new teams or update existing ones.** + + To simplify the move, Aiven will also begin migrating your existing teams to groups. + +- **After DATE Y, all teams will be migrated to groups and deleted.** + + To make the transition to groups smoother, you can + [migrate your teams](#migrate-teams-to-groups) yourself. ::: ## Create a team +1. In the organization, click **Admin**. +1. Click **Teams**. 1. Click **Create new team**. 1. Enter a **Team Name**. 1. Click **Create team**. ## Add users to a team +Users must be part of an organization before being added to a team. + +1. In the organization, click **Admin**. +1. Click **Teams**. 1. Click the name of the team to add users to. 1. On the **Team Members** tab, click **Invite users**. 1. Enter the email address of the user and click **Invite users**. @@ -36,10 +47,6 @@ The user will get an email with an invitation link. ## Add projects and roles to a team -:::important -Teams cannot be assigned to units. -::: - For each team you can specify which projects they can access and the level of permissions: @@ -58,10 +65,7 @@ To add projects and roles to a team: 1. Select a **Project Name** and **Permission Level**. 1. Click **Add project to team**. -You can edit the permissions or delete the project from this team by -clicking the more options menu for the project. - -## Migrate teams to groups {#migrate_teams_to_groups} +## Migrate teams to groups 1. In the organization, click **Admin**. @@ -72,10 +76,10 @@ clicking the more options menu for the project. - the permission level that is assigned for each project :::note - Users on the Account Owners team automatically become super admin with full access to - manage the organization. You don't need to create a group for these users or manage - this team after the migration. Instead, you can - [make users super admin](/docs/platform/howto/make-super-admin). + Users on the Account Owners team automatically become + [super admin](/docs/platform/howto/make-super-admin) with full access to + manage the organization. You don't need to create a group for these users. + They will still have this level of access after the migration. ::: 1. Click **Groups**. diff --git a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md index df64d364..8719b162 100644 --- a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md +++ b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md @@ -5,7 +5,28 @@ sidebar_label: Migrate from teams to groups Teams in Aiven are becoming groups. [Groups](/docs/platform/howto/manage-groups) are an easier way to control access to your organization's projects and services for a group of users. -To get started using organization groups, replace your existing teams with groups. +:::important[Teams have been deprecated and are being migrated to groups.] + +- **On DATE Z the Account Owners team will be removed.** + + The Account Owners and super admin + are synced, so the removal of the Account Owners team will have no impact on your + operations. [Super admin](/docs/platform/concepts/orgs-units-projects#users-and-roles) + have full access to organizations. + +- **From DATE X you won’t be able to create new teams or update existing ones.** + + To simplify the move, Aiven will also begin migrating your existing teams to groups. + +- **After DATE Y, all teams will be migrated to groups and deleted.** + + To make the transition to groups smoother, you can + migrate your teams before this date. If you choose not to migrate to groups yourself + then you will have to [update your resources](#update-teams-resources) + after Aiven removes your teams. +::: + +## Migrate teams to groups 1. For each team, make a note of: @@ -54,3 +75,137 @@ To get started using organization groups, replace your existing teams with group ``` 1. After confirming all users have the correct access, delete the team resources. + +## Update teams resources + +After the automatic migration from teams to groups you will need to +update your Terraform files with the groups resources. + +Groups created during the migration have the same name of the teams. + + +:::tip +Backup your Terraform state file `terraform.tfstate` to use in the case +of a rollback. +::: + + +The following is an example file with a team that has one member +and one project. + +```hcl +terraform { + required_providers { + aiven = { + source = "aiven/aiven" + version = ">=4.0.0, <5.0.0" + } + } +} + +provider "aiven" { + api_token = var.aiven_token +} + +# Your account +data "aiven_account" "main" { + name = "Example Account" +} + +# Your project +data "aiven_project" "example_project" { + project = "example-project" +} + +# Team +resource "aiven_account_team" "example_team" { + account_id = data.aiven_account.main.account_id + name = "Example team" +} + +# Team member +resource "aiven_account_team_member" "main" { + account_id = data.aiven_account.main.account_id + team_id = aiven_account_team.example_team.team_id + user_email = "amal@example.com" +} + +# Project added to the team +resource "aiven_account_team_project" "main" { + account_id = data.aiven_account.main.account_id + team_id = aiven_account_team.example_team.team_id + project_name = data.aiven_project.example_project.project + team_type = "admin" +} +``` + +1. Replace the `aiven_account_team` resources with + `aiven_organization_user_group`: + ```hcl + # The new group created from a team of the same name. + resource "aiven_organization_user_group" "example_group" { + description = "Example group migrated from teams." + organization_id = data.aiven_organization.main.id + name = "Example group" + } + ``` + +1. Replace the `aiven_account_team_member` resources with + `aiven_organization_user_group_member`: + ```hcl + resource "aiven_organization_user_group_member" "project_admin" { + group_id = aiven_organization_user_group.example_group.group_id + organization_id = data.aiven_organization.main.id + user_id = "u123a456b7890c" + } + ``` + +1. Replace the `aiven_account_team_project` resources with + `aiven_organization_group_project`: + ```hcl + resource "aiven_organization_group_project" "example" { + group_id = aiven_organization_user_group.example_group.group_id + project = data.aiven_project.example_project.project + role = "admin" + } + ``` + +1. To list all resources in the state file, run: + + ```bash + terraform console + terraform state list + ``` + +3. Remove Terraform's control of the team resources in this list by running: + + ``` + terraform state rm TEAM_RESOURCE + ``` + + Where TEAM_RESOURCE is your resource, for example: `aiven_account_team.example_team`. + + :::tip + Use the `-dry-run` flag to preview the changes without applying + them. + ::: + +4. Add the group resources to Terraform by importing them: + + ``` + terraform import aiven_organization_user_group.example ORGANIZATION_ID/USER_GROUP_ID + terraform import aiven_organization_user_group_member.project_admin ORGANIZATION_ID/USER_GROUP_ID/USER_ID + terraform import aiven_organization_group_project.example PROJECT/USER_GROUP_ID + ``` + +5. Check that the import is going to run as you expect: + + ``` + terraform plan + ``` + +6. Apply the new configuration: + + ``` + terraform apply + ``` From 8f9aa97d58c263d966aa2252fa89c1bf10a1ba9f Mon Sep 17 00:00:00 2001 From: Stacey Salamon Date: Thu, 6 Jun 2024 11:04:49 +0200 Subject: [PATCH 2/6] finalize instructions for udpating resources in TF --- .../howto/migrate-from-teams-to-groups.md | 48 ++++++++++++++----- 1 file changed, 37 insertions(+), 11 deletions(-) diff --git a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md index 8719b162..f6bf40f5 100644 --- a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md +++ b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md @@ -141,6 +141,7 @@ resource "aiven_account_team_project" "main" { 1. Replace the `aiven_account_team` resources with `aiven_organization_user_group`: + ```hcl # The new group created from a team of the same name. resource "aiven_organization_user_group" "example_group" { @@ -151,7 +152,8 @@ resource "aiven_account_team_project" "main" { ``` 1. Replace the `aiven_account_team_member` resources with - `aiven_organization_user_group_member`: + `aiven_organization_user_group_member`: + ```hcl resource "aiven_organization_user_group_member" "project_admin" { group_id = aiven_organization_user_group.example_group.group_id @@ -162,6 +164,7 @@ resource "aiven_account_team_project" "main" { 1. Replace the `aiven_account_team_project` resources with `aiven_organization_group_project`: + ```hcl resource "aiven_organization_group_project" "example" { group_id = aiven_organization_user_group.example_group.group_id @@ -173,13 +176,12 @@ resource "aiven_account_team_project" "main" { 1. To list all resources in the state file, run: ```bash - terraform console terraform state list ``` -3. Remove Terraform's control of the team resources in this list by running: +1. Remove Terraform's control of the team resources in this list by running: - ``` + ```bash terraform state rm TEAM_RESOURCE ``` @@ -190,22 +192,46 @@ resource "aiven_account_team_project" "main" { them. ::: -4. Add the group resources to Terraform by importing them: +1. Add the group resources to Terraform by importing them. + - For groups, run: + ```bash + terraform import aiven_organization_user_group.EXAMPLE ORGANIZATION_ID/USER_GROUP_ID ``` - terraform import aiven_organization_user_group.example ORGANIZATION_ID/USER_GROUP_ID - terraform import aiven_organization_user_group_member.project_admin ORGANIZATION_ID/USER_GROUP_ID/USER_ID - terraform import aiven_organization_group_project.example PROJECT/USER_GROUP_ID + + - For group members, run: + ```bash + terraform import aiven_organization_user_group_member.EXAMPLE ORGANIZATION_ID/USER_GROUP_ID/USER_ID ``` -5. Check that the import is going to run as you expect: + - For projects assigned to the groups: + ```bash + terraform import aiven_organization_group_project.EXAMPLE PROJECT/USER_GROUP_ID ``` + + Where: + - `EXAMPLE` is the resource name. + - `ORGANIZATION_ID` is the ID of the organization the group is in. Organization is the + new name for accounts. + - `USER_GROUP_ID` is the ID of the user group in the format `ug123a456b7890c`. + - `USER_ID` is the ID of the user in the format `u123a456b7890c`. + - `PROJECT` is the name of the project. + +1. To preview the changes, run: + + ```bash terraform plan ``` -6. Apply the new configuration: +1. To apply the changes, run: + ```bash + terraform apply --auto-approve ``` - terraform apply + +1. To confirm the changes, run: + + ```bash + terraform state list ``` From ac95ca38ca54e190459ce4db85fcfdf06d16fddd Mon Sep 17 00:00:00 2001 From: Stacey Salamon Date: Thu, 6 Jun 2024 12:12:20 +0200 Subject: [PATCH 3/6] formatting and other fixes to update instructions --- .../howto/migrate-from-teams-to-groups.md | 49 ++++++++++--------- 1 file changed, 25 insertions(+), 24 deletions(-) diff --git a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md index f6bf40f5..f6180c18 100644 --- a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md +++ b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md @@ -79,19 +79,12 @@ Teams in Aiven are becoming groups. [Groups](/docs/platform/howto/manage-groups) ## Update teams resources After the automatic migration from teams to groups you will need to -update your Terraform files with the groups resources. +update your Terraform files with the groups resources. Groups created during the +migration have the same name of the teams. They also have the same users +and projects assigned to them. -Groups created during the migration have the same name of the teams. - - -:::tip -Backup your Terraform state file `terraform.tfstate` to use in the case -of a rollback. -::: - - -The following is an example file with a team that has one member -and one project. +The following shows how to change your team resources to groups +using this example file with a team that has one member and one project. ```hcl terraform { @@ -138,11 +131,20 @@ resource "aiven_account_team_project" "main" { team_type = "admin" } ``` +:::tip +Backup your Terraform state file `terraform.tfstate` to use in the case +of a rollback. +::: 1. Replace the `aiven_account_team` resources with `aiven_organization_user_group`: ```hcl + # Your organization. + data "aiven_organization" "main" { + name = "Example organization" + } + # The new group created from a team of the same name. resource "aiven_organization_user_group" "example_group" { description = "Example group migrated from teams." @@ -195,25 +197,24 @@ resource "aiven_account_team_project" "main" { 1. Add the group resources to Terraform by importing them. - For groups, run: - ```bash - terraform import aiven_organization_user_group.EXAMPLE ORGANIZATION_ID/USER_GROUP_ID - ``` + ```bash + terraform import aiven_organization_user_group.EXAMPLE ORGANIZATION_ID/USER_GROUP_ID + ``` - For group members, run: - ```bash - terraform import aiven_organization_user_group_member.EXAMPLE ORGANIZATION_ID/USER_GROUP_ID/USER_ID - ``` + ```bash + terraform import aiven_organization_user_group_member.EXAMPLE ORGANIZATION_ID/USER_GROUP_ID/USER_ID + ``` - For projects assigned to the groups: - ```bash - terraform import aiven_organization_group_project.EXAMPLE PROJECT/USER_GROUP_ID - ``` + ```bash + terraform import aiven_organization_group_project.EXAMPLE PROJECT/USER_GROUP_ID + ``` Where: - `EXAMPLE` is the resource name. - - `ORGANIZATION_ID` is the ID of the organization the group is in. Organization is the - new name for accounts. + - `ORGANIZATION_ID` is the ID of the organization the group is in. - `USER_GROUP_ID` is the ID of the user group in the format `ug123a456b7890c`. - `USER_ID` is the ID of the user in the format `u123a456b7890c`. - `PROJECT` is the name of the project. @@ -230,7 +231,7 @@ resource "aiven_account_team_project" "main" { terraform apply --auto-approve ``` -1. To confirm the changes, run: +1. To confirm the changes, list the resources in the state file by running: ```bash terraform state list From 04c643d0bc1331bec5384ab0a658ff67b5e60aeb Mon Sep 17 00:00:00 2001 From: Stacey Salamon Date: Mon, 10 Jun 2024 14:11:52 +0200 Subject: [PATCH 4/6] add dates --- docs/tools/aiven-console/howto/create-manage-teams.md | 6 +++--- docs/tools/terraform/howto/migrate-from-teams-to-groups.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/tools/aiven-console/howto/create-manage-teams.md b/docs/tools/aiven-console/howto/create-manage-teams.md index 6286d037..0f649bd3 100644 --- a/docs/tools/aiven-console/howto/create-manage-teams.md +++ b/docs/tools/aiven-console/howto/create-manage-teams.md @@ -8,18 +8,18 @@ Teams are groups of users that you can assign to projects. :::important[Teams have been deprecated and are being migrated to groups] -- **On DATE Z the Account Owners team will be removed.** +- **On September 2, 2024 the Account Owners team will be removed.** The Account Owners and super admin are synced, so the removal of the Account Owners team will have no impact on your operations. [Super admin](/docs/platform/concepts/orgs-units-projects#users-and-roles) have full access to organizations. -- **From DATE X you won’t be able to create new teams or update existing ones.** +- **From November 4, 2024 you won’t be able to create new teams or update existing ones.** To simplify the move, Aiven will also begin migrating your existing teams to groups. -- **After DATE Y, all teams will be migrated to groups and deleted.** +- **On December 2, 2024 all teams will be migrated to groups and deleted.** To make the transition to groups smoother, you can [migrate your teams](#migrate-teams-to-groups) yourself. diff --git a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md index f6180c18..ebb8bf6d 100644 --- a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md +++ b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md @@ -7,18 +7,18 @@ Teams in Aiven are becoming groups. [Groups](/docs/platform/howto/manage-groups) :::important[Teams have been deprecated and are being migrated to groups.] -- **On DATE Z the Account Owners team will be removed.** +- **On September 2, 2024 the Account Owners team will be removed.** The Account Owners and super admin are synced, so the removal of the Account Owners team will have no impact on your operations. [Super admin](/docs/platform/concepts/orgs-units-projects#users-and-roles) have full access to organizations. -- **From DATE X you won’t be able to create new teams or update existing ones.** +- **From November 4, 2024 you won’t be able to create new teams or update existing ones.** To simplify the move, Aiven will also begin migrating your existing teams to groups. -- **After DATE Y, all teams will be migrated to groups and deleted.** +- **On December 2, 2024 all teams will be migrated to groups and deleted.** To make the transition to groups smoother, you can migrate your teams before this date. If you choose not to migrate to groups yourself From 3a395858eca6fc9b23334434ac162f958861fced Mon Sep 17 00:00:00 2001 From: Stacey Salamon Date: Mon, 10 Jun 2024 16:26:23 +0200 Subject: [PATCH 5/6] improve TF instructions based on feedback --- .../howto/migrate-from-teams-to-groups.md | 23 ++++++++++--------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md index ebb8bf6d..3a86e905 100644 --- a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md +++ b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md @@ -117,7 +117,7 @@ resource "aiven_account_team" "example_team" { } # Team member -resource "aiven_account_team_member" "main" { +resource "aiven_account_team_member" "example_project_member" { account_id = data.aiven_account.main.account_id team_id = aiven_account_team.example_team.team_id user_email = "amal@example.com" @@ -147,9 +147,9 @@ of a rollback. # The new group created from a team of the same name. resource "aiven_organization_user_group" "example_group" { - description = "Example group migrated from teams." - organization_id = data.aiven_organization.main.id name = "Example group" + description = "" + organization_id = data.aiven_organization.main.id } ``` @@ -181,14 +181,16 @@ of a rollback. terraform state list ``` -1. Remove Terraform's control of the team resources in this list by running: +1. To remove Terraform's control of the team resources in this list run + the following command for the `aiven_account_team`, `aiven_account_team_member`, + and `aiven_account_team_project` resources in the state file: ```bash - terraform state rm TEAM_RESOURCE + terraform state rm aiven_account_team.example_team + terraform state rm aiven_account_team_member.main + terraform state rm aiven_account_team_project.main ``` - Where TEAM_RESOURCE is your resource, for example: `aiven_account_team.example_team`. - :::tip Use the `-dry-run` flag to preview the changes without applying them. @@ -198,22 +200,21 @@ of a rollback. - For groups, run: ```bash - terraform import aiven_organization_user_group.EXAMPLE ORGANIZATION_ID/USER_GROUP_ID + terraform import aiven_organization_user_group.example_group ORGANIZATION_ID/USER_GROUP_ID ``` - For group members, run: ```bash - terraform import aiven_organization_user_group_member.EXAMPLE ORGANIZATION_ID/USER_GROUP_ID/USER_ID + terraform import aiven_organization_user_group_member.project_admin ORGANIZATION_ID/USER_GROUP_ID/USER_ID ``` - For projects assigned to the groups: ```bash - terraform import aiven_organization_group_project.EXAMPLE PROJECT/USER_GROUP_ID + terraform import aiven_organization_group_project.main PROJECT/USER_GROUP_ID ``` Where: - - `EXAMPLE` is the resource name. - `ORGANIZATION_ID` is the ID of the organization the group is in. - `USER_GROUP_ID` is the ID of the user group in the format `ug123a456b7890c`. - `USER_ID` is the ID of the user in the format `u123a456b7890c`. From e1c31b944a2cfda92435a1509cb915edfdb6494a Mon Sep 17 00:00:00 2001 From: Stacey Salamon Date: Wed, 12 Jun 2024 11:32:48 +0200 Subject: [PATCH 6/6] fix formatting --- .../howto/create-manage-teams.md | 52 +++++++++---------- .../howto/migrate-from-teams-to-groups.md | 7 +-- 2 files changed, 26 insertions(+), 33 deletions(-) diff --git a/docs/tools/aiven-console/howto/create-manage-teams.md b/docs/tools/aiven-console/howto/create-manage-teams.md index 0f649bd3..9782d9fc 100644 --- a/docs/tools/aiven-console/howto/create-manage-teams.md +++ b/docs/tools/aiven-console/howto/create-manage-teams.md @@ -2,43 +2,32 @@ title: Create and manage teams --- -import ConsoleLabel from "@site/src/components/ConsoleIcons" +**Teams** let you create user groups and assign different access levels to specific projects. -Teams are groups of users that you can assign to projects. +Users must be part of an organization before being added to a team. To create and manage +teams, click **Admin** and select **Teams**. -:::important[Teams have been deprecated and are being migrated to groups] +The members of the Account Owners team are automatically made super admin. Adding other +users to this team makes them a super admin with full access to your organization, +its units, and projects. Likewise, when you make a user a super admin, they are added +to the account owners team. -- **On September 2, 2024 the Account Owners team will be removed.** +:::important +**Teams are becoming groups** - The Account Owners and super admin - are synced, so the removal of the Account Owners team will have no impact on your - operations. [Super admin](/docs/platform/concepts/orgs-units-projects#users-and-roles) - have full access to organizations. - -- **From November 4, 2024 you won’t be able to create new teams or update existing ones.** - - To simplify the move, Aiven will also begin migrating your existing teams to groups. - -- **On December 2, 2024 all teams will be migrated to groups and deleted.** - - To make the transition to groups smoother, you can - [migrate your teams](#migrate-teams-to-groups) yourself. +Groups are an easier way to control access to your organization's +projects and services for a group of users. +[Migrate your teams to groups](#migrate_teams_to_groups). ::: ## Create a team -1. In the organization, click **Admin**. -1. Click **Teams**. 1. Click **Create new team**. 1. Enter a **Team Name**. 1. Click **Create team**. ## Add users to a team -Users must be part of an organization before being added to a team. - -1. In the organization, click **Admin**. -1. Click **Teams**. 1. Click the name of the team to add users to. 1. On the **Team Members** tab, click **Invite users**. 1. Enter the email address of the user and click **Invite users**. @@ -47,6 +36,10 @@ The user will get an email with an invitation link. ## Add projects and roles to a team +:::important +Teams cannot be assigned to units. +::: + For each team you can specify which projects they can access and the level of permissions: @@ -65,7 +58,10 @@ To add projects and roles to a team: 1. Select a **Project Name** and **Permission Level**. 1. Click **Add project to team**. -## Migrate teams to groups +You can edit the permissions or delete the project from this team by +clicking the more options menu for the project. + +## Migrate teams to groups {#migrate_teams_to_groups} 1. In the organization, click **Admin**. @@ -76,10 +72,10 @@ To add projects and roles to a team: - the permission level that is assigned for each project :::note - Users on the Account Owners team automatically become - [super admin](/docs/platform/howto/make-super-admin) with full access to - manage the organization. You don't need to create a group for these users. - They will still have this level of access after the migration. + Users on the Account Owners team automatically become super admin with full access to + manage the organization. You don't need to create a group for these users or manage + this team after the migration. Instead, you can + [make users super admin](/docs/platform/howto/make-super-admin). ::: 1. Click **Groups**. diff --git a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md index 3a86e905..2705a3e8 100644 --- a/docs/tools/terraform/howto/migrate-from-teams-to-groups.md +++ b/docs/tools/terraform/howto/migrate-from-teams-to-groups.md @@ -5,7 +5,8 @@ sidebar_label: Migrate from teams to groups Teams in Aiven are becoming groups. [Groups](/docs/platform/howto/manage-groups) are an easier way to control access to your organization's projects and services for a group of users. -:::important[Teams have been deprecated and are being migrated to groups.] +:::important +**Teams have been deprecated and are being migrated to groups.** - **On September 2, 2024 the Account Owners team will be removed.** @@ -131,10 +132,6 @@ resource "aiven_account_team_project" "main" { team_type = "admin" } ``` -:::tip -Backup your Terraform state file `terraform.tfstate` to use in the case -of a rollback. -::: 1. Replace the `aiven_account_team` resources with `aiven_organization_user_group`: