Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HOTFIX]: Add manual trigger for cache updater stack #1001

Merged
merged 10 commits into from
Feb 27, 2024

Conversation

branberry
Copy link
Contributor

@branberry branberry commented Feb 23, 2024

Stories/Links:

Notes

This PR resolves the issue related to 10gen repositories not being built. For confirmation, I tested the process manually, and the updated cache files for 10gen repos are now present. To verify, view the snooty-parse-cache S3 bucket in the AWS console, and confirm that the .snooty-cloud-docs-... ZIP file is present within the repository, and that it was updated today (February 23rd).

README updates

    • This PR introduces changes that should be reflected in the README, and I have made those updates.

Copy link

Your feature branch infrastructure has been deployed!

Your webhook URL is: https://903kan80ec.execute-api.us-east-2.amazonaws.com/prod/webhook/githubEndpoint/trigger/build

For more information on how to use this endpoint, follow these instructions.

forceRun:
description: Force the cache to be rebuilt.
default: 'false'
push:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOTE: Remove this before merging

@@ -20,7 +29,9 @@ jobs:
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
aws-region: us-east-2
- name: Rebuild Cache if New Snooty Parser Version
uses: mongodb/docs-worker-actions/rebuild-parse-cache@main
uses: mongodb/docs-worker-actions/rebuild-parse-cache@cache-update-hotfix
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOTE: revert this after merging this PR

@branberry branberry marked this pull request as ready for review February 23, 2024 19:55
Copy link
Contributor

@rayangler rayangler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the context on the problem. Lgtm with one nit

Comment on lines 16 to 17
const errorMessage = `ERROR! GITHUB_BOT_USERNAME is not set. ${repoOwner}/${repoName} will not have their cache updated`;
console.error(`ERROR! GITHUB_BOT_USERNAME is not set. ${repoOwner}/${repoName} will not have their cache updated`);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Nit) Should we consolidate to console.error(errorMessage)?

@branberry branberry merged commit 30b371b into main Feb 27, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants