[GitHub] [airflow] turbaszek commented on pull request #20769: [wip] [Part 2] Calendar to GCS Operator

[GitBox <gi...@apache.org>]

turbaszek commented on pull request #20769:
URL: https://github.com/apache/airflow/pull/20769#issuecomment-1008326166


   > 
   > I read through this [guide](https://github.com/apache/airflow/blob/main/TESTING.rst#airflow-system-tests). I think I need make some changes to variables.env file; but I am not sure what these changes should be.
   
   From your example DAG it looks like you need to set up two variables:
   - GCP_GCS_BUCKET
   - CALENDAR_ID
   
   Apart from that you will need to add a credentials key because you are using it in test:
   ```py
   @pytest.mark.credential_file(GCP_GCS_KEY)
   ```
   The file should be named `gcp_gcs.json` and put according to the guid you linked:
   
   > If your system tests need some credential files to be available for an authentication with external systems, make sure to keep these credentials in the files/airflow-breeze-config/keys directory. Mark your tests with @pytest.mark.credential_file(<FILE>) so that they are skipped if such a credential file is not there. The tests should read the right credentials and authenticate them on their own. The credentials are read in Breeze from the /files directory. The local "files" folder is mounted to the "/files" folder in Breeze.
   
   
   > Also, I am not sure about the --forward-credentials option for [running system tests](https://github.com/apache/airflow/blob/main/TESTING.rst#the-typical-system-test-session). Which credentials will it forward? Do I need to put the credentials somewhere?
   
   You need to use credentials to some GCP project. As far as I know we don't have airflow project that can be used for this purpose (cc @potiuk to confirm).
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org