From 3273df4b5caeea266ef792d7762095132a48d015 Mon Sep 17 00:00:00 2001 From: Jonathan Rosenberg <96974219+Jonathan-Rosenberg@users.noreply.github.com> Date: Wed, 6 Dec 2023 12:48:31 +0200 Subject: [PATCH] change demo.lakefs.io to lakefs.cloud --- docs/understand/use_cases/etl_testing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/understand/use_cases/etl_testing.md b/docs/understand/use_cases/etl_testing.md index a63a6220bbf..1575051dbc4 100644 --- a/docs/understand/use_cases/etl_testing.md +++ b/docs/understand/use_cases/etl_testing.md @@ -53,9 +53,9 @@ You can also [deploy lakeFS]({% link howto/deploy/index.md %}) locally or self-m ### Using lakeFS Playground on lakeFS Cloud -In this tutorial, we will use [a lakeFS playground environment](https://demo.lakefs.io/) to create dev/test data environments for ETL testing. This allows you to spin up a lakeFS instance in a click, create different data environments by simply branching out of your data repository and develop & test data pipelines in these isolated branches. +In this tutorial, we will use [a lakeFS playground environment](https://lakefs.cloud/) to create dev/test data environments for ETL testing. This allows you to spin up a lakeFS instance in a click, create different data environments by simply branching out of your data repository and develop & test data pipelines in these isolated branches. -First, let us spin up a [playground](https://demo.lakefs.io/) instance. Once you have a live environment, login to your instance with access and secret keys. Then, you can work with the sample data repository `my-repo` that is created for you. +First, let us spin up a [playground](https://lakefs.cloud/) instance. Once you have a live environment, login to your instance with access and secret keys. Then, you can work with the sample data repository `my-repo` that is created for you. ![sample repository]({{ site.baseurl }}/assets/img/iso_env_myrepo.png)