Skip to content

Commit afa0331

Browse files
committed
review comments
1 parent b2d16ee commit afa0331

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

articles/api-management/breaking-changes/workspaces-breaking-changes-june-2024.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -74,11 +74,11 @@ The Developer tier was designed for single-user or single-team use cases. It's u
7474

7575
* **Aggregate in a Premium tier instance**
7676

77-
Aggregate multiple nonproduction environments in a single Premium tier instance. Use workspaces in the Premium tier to isolate the different environments.
77+
While upgrading each Developer tier instance to Premium tier is an option, consider aggregating multiple nonproduction environments in a single Premium tier instance. Use workspaces in the Premium tier to isolate the different environments.
7878

79-
* **Use Developer tier instances for development, migrate to workspaces in Premium tier**
79+
* **Use Developer tier instances for development, migrate to workspaces in Premium tier for production**
8080

81-
You might use Developer tier instances for development environments. For higher environments, you can migrate the configuration of these Developer-tier services into workspaces of a Premium tier service. With this approach you may run into issues or conflicts when managing the configurations across environments.
81+
You might use Developer tier instances for development environments. For higher environments, you can migrate the configuration of each Developer-tier service into a workspace of a Premium tier service, for example, using CI/CD pipelines. With this approach you may run into issues or conflicts when managing the configurations across environments.
8282

8383
If you're currently using workspaces in a Developer tier instance, you can migrate the workspace configurations to a Developer tier instance without workspaces:
8484

@@ -96,7 +96,6 @@ If you assigned workspace-level entities to service-level entities in the worksp
9696
|---------|---------|
9797
|Assign workspace APIs to service-level products | Use workspace-level products |
9898
|Assign workspace APIs or products to service-level tags | Use workspace-level tags |
99-
|Assign service-level groups to workspace products for visibility controls | |
10099

101100
## Help and support
102101

0 commit comments

Comments
 (0)