image reference fix

dagster-io · Jan 22, 2025 · e772fa8 · e772fa8
1 parent 3a7b602
commit e772fa8
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/...docs/dagster-plus/deployment/management/managing-multiple-projects-and-teams.md b/...docs/dagster-plus/deployment/management/managing-multiple-projects-and-teams.md
@@ -207,7 +207,7 @@ In order from least to most isolated, there are three levels of isolation:
 
 If you have no specific requirements for isolation beyond the ability to deploy and run multiple projects, you can use a single agent and deployment to manage all your projects as individual code locations.
 
-![Diagram of isolation at the code location level](/images/dagster-cloud/managing-deployments/isolation-level-code-locations.png)
+![Diagram of isolation at the code location level](/images/dagster-plus/deployment/management/managing-deployments/isolation-level-code-locations.png)
 
 <table
   className="table"
@@ -280,7 +280,7 @@ Motivations for utilizing this approach could include:
 - Different compute requirements, such as different cloud providers or architectures
 - Optimizing for locality or access, such as running the data processing closer or in environment with access to the storage locations
 
-![Diagram of isolation at the agent level](/images/dagster-cloud/managing-deployments/isolation-level-agents.png)
+![Diagram of isolation at the agent level](/images/dagster-plus/deployment/management/managing-deployments/isolation-level-agents.png)
 
 <table
   className="table"
@@ -334,7 +334,7 @@ Multiple deployments are only available in Dagster+ Pro.
 
 Of the approaches outlined in this guide, multiple deployments are the most isolated solution. The typical motivation for this isolation level is to separate production and non-production environments. It may be considered to satisfy other organization specific requirements.
 
-![Diagram of isolation at the Dagster+ deployment level](/images/dagster-cloud/managing-deployments/isolation-level-deployments.png)
+![Diagram of isolation at the Dagster+ deployment level](/images/dagster-plus/deployment/management/managing-deployments/isolation-level-deployments.png)
 
 <table
   className="table"

diff --git a/...plus/features/ci-cd/branch-deployments/using-branch-deployments-with-the-cli.md b/...plus/features/ci-cd/branch-deployments/using-branch-deployments-with-the-cli.md
@@ -62,7 +62,7 @@ Using the tabs, select your agent type to view instructions.
 
    In the list, locate the repository and its **URI**:
 
-   ![Highlighted repository URI in the AWS ECR console](/images/dagster-plus/branch-deployments/aws-ecr-uri.png)
+   ![Highlighted repository URI in the AWS ECR console](/images/dagster-plus/features/branch-deployments/aws-ecr-uri.png)
 
 3. [**Create an IAM user.**](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html) This user must:
 
@@ -71,7 +71,7 @@ Using the tabs, select your agent type to view instructions.
 
    After the user is created, save the **Access key ID** and **Secret access key** values shown on the confirmation page:
 
-   ![Highlighted repository URI in the AWS ECR console](/images/dagster-plus/branch-deployments/aws-iam-user-keys.png)
+   ![Highlighted repository URI in the AWS ECR console](/images/dagster-plus/features/branch-deployments/aws-iam-user-keys.png)
 
 </TabItem>
 <TabItem value="Docker">
@@ -210,4 +210,4 @@ Now that Branch Deployments are configured, you can check out the preview in Dag
 
 Click the **deployment switcher** to view your workspace's branch deployments:
 
-![Highlighted branch deployments in the Dagster+'s deployment switcher](/images/dagster-plus/branch-deployments/dagster-ui-deployment-switcher.png)
+![Highlighted branch deployments in the Dagster+'s deployment switcher](/images/dagster-plus/features/branch-deployments/dagster-ui-deployment-switcher.png)