From e1de72f4bcce11999b54fdc450fb33627188837b Mon Sep 17 00:00:00 2001
From: trentmc <5305452+trentmc@users.noreply.github.com>
Date: Sun, 25 Oct 2020 16:19:12 +0100
Subject: [PATCH] set v3 expectations

---
 content/tutorials/on-premise-for-brizo.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/tutorials/on-premise-for-brizo.md b/content/tutorials/on-premise-for-brizo.md
index f2d141a9..cbcda2db 100644
--- a/content/tutorials/on-premise-for-brizo.md
+++ b/content/tutorials/on-premise-for-brizo.md
@@ -3,6 +3,8 @@ title: Set Up On-Premise Storage
 description: Tutorial about how to set up on-premise storage for use with Ocean Protocol.
 ---
 
+*Note: This needs updating for Ocean V3. As a workaround: Brizo has been renamed to provider-py; it should work similarly.*
+
 To enable Brizo to use files stored in on-premise storage (i.e. files with an URL not containing `core.windows.net` or `s3://`), there is _nothing to do, other than make sure Brizo can resolve the URLs_. In particular, you don't have to set any Brizo-specific configuration settings, e.g. in the `[osmosis]` section of the Brizo config file or in some special Brizo environment variables.
 
 Local and private network URLs are fine so long as they can be resolved by Brizo. Potential examples include `http://localhost/helicopter_data.xls`, `http://192.168.12.34/almond_sales_2012.csv` and `http://10.12.34.56/duck_photos.zip`.