Downloading and checking files from cloud instances#
Note
In this tutorial, we are using the SHAREPOINT_FETCHER_PROJECT_URL
variable to specify the URL for the data we are going to fetch. Another way to achieve this is by setting the SHAREPOINT_FETCHER_PROJECT_SITE
and SHAREPOINT_FETCHER_PROJECT_PATH
variables. Although the SHAREPOINT_FETCHER_PROJECT_URL
takes precedence, both methods yield the same results, and it is up to you which method you choose. If you are familiar retrieving the URL directly from the SharePoint interface in the correct format, we recommend using the first approach. Otherwise, manually constructing the URL based on the project site and path might be the better solution for you. For more information, please refer to SharePoint Fetcher Background Information.
Note
If you want a tutorial with example data for an on-premise instance of SharePoint please check Downloading and checking files from on-premise instances.
Introduction#
With the SharePoint fetcher and evaluator, you can fetch files from a SharePoint site that you have access to and subsequently evaluate them based on their SharePoint-related properties (last modified date, revision status, archiving period etc.).
Use-case#
For this example, we are using the following use case:
The SharePoint fetcher downloads a specific file from cloud SharePoint and evaluates it based on its
lastModifiedDateTime
property.We want to verify that its last modification took place within the last 12 months.
This can for example be useful if you have a document like the state-of-the-art (SOTA) assessment for your project that you update once a year and you want to ensure that the content isn’t outdated.
Note
The SharePoint config files in this example need to be adapted to your network environment and your server locations. Please make sure to adapt the files accordingly.
Preparation#
Download resources#
Please go ahead and download the following files. They will be required in the subsequent steps.
Adjusting the config files#
The qg-config.yaml#
You need to set a few environment variables in the qg-config.yaml
. Feel free
to have a look at the downloaded file first, to get an overview of it.
Subsequently we will go over the parts that you want to adjust step by step.
If you want to find out more about how you can configure the Registration App in Azure Active Directory and how to get the credentials, please have a look at: How to configure an Azure App Registration required for authentication.
12 SHAREPOINT_FETCHER_TENANT_ID: ${{ secrets.SHAREPOINT_FETCHER_TENANT_ID }}
13 SHAREPOINT_FETCHER_CLIENT_ID: ${{ secrets.SHAREPOINT_FETCHER_CLIENT_ID }}
14 SHAREPOINT_FETCHER_CLIENT_SECRET: ${{ secrets.SHAREPOINT_FETCHER_CLIENT_SECRET}}
Lines 12-14 require credentials from the AAD Registration App: tenant id for the variable SHAREPOINT_FETCHER_TENANT_ID
, client id for the variable SHAREPOINT_FETCHER_CLIENT_ID
and client secret value for the variable SHAREPOINT_FETCHER_CLIENT_SECRET
. Open your Yaku UI and add them to the Secrets to your namespace. If you need help with that, check out: Creating secrets.
15 SHAREPOINT_FETCHER_PROJECT_URL: https://mycompany.sharepoint.com/:w:/r/sites/msteams_5xxxxxx5/Shared%20Documents/SomeDocument.docx?d=wcf5222222222222222222222222659a6&csf=1&web=1&e=UgcMLr
16 SHAREPOINT_FETCHER_IS_CLOUD: 'True'
Please add the URL of the project site that you want to use in this example in line 15. For more information about how to retrieve the SHAREPOINT_FETCHER_PROJECT_URL
variable and what format it requires, please check How to get the URL of a file or folder from cloud SharePoint. In line 16 you need to set the SHAREPOINT_FETCHER_IS_CLOUD
variable to “True” since we want to fetch data from a cloud SharePoint instance.
Running the example#
Now, you can run the example. Upload the sharepoint-evaluator-config-file.yaml
, using the same name as stated in the SHAREPOINT_EVALUATOR_CONFIG_FILE
variable (line 17 in the qg-config.yaml
) as well as the qg-config.yaml
.