Update Algolia index as part of the website deployment pipeline #2434
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We can avoid having to run Algolia as a separate scheduled job and instead update the index whenever a new version of the Taquito website is published.
According to the docs when a new index is created, it overwrites the previous one. We don't need to delete the old index before running the
docsearch-scraper
, so I removed the step from the job and deleted thedelete-index.js
script.Test Plan
I tested running the
Update Algolia Index
in a separate workflow file, and I can confirm that it works as expected https://github.com/ecadlabs/taquito/actions/runs/4693185099/jobs/8319833341#step:4:155