🎉 fix for filenames too long in local Win deployment (#3625)

* fix for filenames too long in local Win deployment

* added Azure Blob Storage capability to files source

* azure blob storage files source connector

* Revert "fix for filenames too long in local Win deployment"

This reverts commit 5a36b97.

* Revert "azure blob storage files source connector"

This reverts commit a76130f.

* Revert "Revert "fix for filenames too long in local Win deployment""

This reverts commit 473ef8b.

Co-authored-by: George Claireaux <george.claireaux@effem.com>

docs/deploying-airbyte/local-deployment.md

@@ -22,6 +22,12 @@ docker-compose up
 
 We recommend following [this guide](https://docs.docker.com/docker-for-windows/install/) to install Docker on Windows. After installing the WSL 2 backend and Docker you should be able to run containers using Windows PowerShell. Additionally, as we note frequently, you will need `docker-compose` to build Airbyte from source. The suggested guide already installs `docker-compose` on Windows. 
 
+If you are cloning the repo, you might run into a problem where git indicates that certain Filenames are too long and it therefore can't create the local file. Running the following command in *git bash*:
+```bash
+git config --system core.longpaths true
+```
+and performing a system reboot seems to solve this limitation. However it's worth pointing out that the above setting is defaulted to false for a reason, so use with caution. Find more details on [this stack overflow question](https://stackoverflow.com/questions/22575662/filename-too-long-in-git-for-windows).
+
 Instead of cloning the repo, you can alternatively download the latest Airbyte release [here](https://github.com/airbytehq/airbyte/releases). Unzip the downloaded file, access the unzipped file using PowerShell terminal, and run `docker-compose up`. After this, you should see the Airbyte containers in the Docker application as in the image below.
 
 ![](../.gitbook/assets/airbyte_deploy_windows_docker.png)