gopidesupavan commented on code in PR #1181:
URL: https://github.com/apache/airflow-site/pull/1181#discussion_r2072352440


##########
.github/workflows/build.yml:
##########
@@ -107,6 +107,30 @@ jobs:
           rm -rf ./docs-archive/*
           echo "docs-archive directory files are deleted as they are no longer 
needed after the site is built in the above step"
           /mnt/airflow-site/.github/scripts/print_df.sh
+
+      - name: Install AWS CLI v2
+        if: ${{ github.event_name == 'push' }}
+        run: |
+          curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip"; -o 
/tmp/awscliv2.zip
+          unzip -q /tmp/awscliv2.zip -d /tmp
+          rm /tmp/awscliv2.zip
+          sudo /tmp/aws/install --update
+          rm -rf /tmp/aws/
+
+      - name: Configure AWS credentials
+        if: ${{ github.event_name == 'push' }}
+        uses: 
aws-actions/configure-aws-credentials@010d0da01d0b5a38af31e9c3470dbfdabdecca3a  
# v4.0.1
+        with:
+          aws-access-key-id: ${{ secrets.DOCS_AWS_ACCESS_KEY_ID }}
+          aws-secret-access-key: ${{ secrets.DOCS_AWS_SECRET_ACCESS_KEY }}
+          aws-region: us-east-2
+
+      - name: Copy docs index page to S3 docs
+        if: ${{ github.event_name == 'push' }}
+        run: |
+          aws s3 cp ./dist/docs/index.html 
s3://staging-docs-airflow-apache-org/docs/index.html
+          aws s3 cp ./dist/docs/index.xml 
s3://staging-docs-airflow-apache-org/docs/index.xml

Review Comment:
   The index.html file generated in this repository is required at the S3 
location; otherwise, we encounter a "Not Found" error. Therefore, the only 
solution i think is to copy this file to S3 as part of the generation process.
   
   I attempted to use a redirect, but it resulted in an infinite loop—this 
behavior is expected since we're proxying through S3.



-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to