You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now to update the search index after changes have been made in the docs, you need to wait for the new chart to be released, and Argo CD to deploy the new version in production. Once it's done, one can run this GitHub Workflow.
So the process is easier than doing it manually on your machine, but it's not automated. The best-case scenario would be to have this workflow run when we know the new docs version is deployed, which would require the release process to fire the workflow, and having this one check with the Argo CD CLI the deployment status, and ran the crawler when the docs is updated. We do not have a CWFT that let us get that information, so it's the easiest way I found so far. Here is an internal question I had to be able to do that.
The second-best way to do that is to have the workflow run automatically every X hours/day, so in most cases it would run without any need to update the index, but nobody would have to run it manually.
For now, keep in mind that every time the docs is updated, the docs owner needs to run the workflow manually to update the search index.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What type of suggestions?
Something's not working
What page is concerned?
No response
What version of the docs?
No response
What is the issue?
Right now to update the search index after changes have been made in the docs, you need to wait for the new chart to be released, and Argo CD to deploy the new version in production. Once it's done, one can run this GitHub Workflow.
So the process is easier than doing it manually on your machine, but it's not automated. The best-case scenario would be to have this workflow run when we know the new docs version is deployed, which would require the release process to fire the workflow, and having this one check with the Argo CD CLI the deployment status, and ran the crawler when the docs is updated. We do not have a CWFT that let us get that information, so it's the easiest way I found so far. Here is an internal question I had to be able to do that.
The second-best way to do that is to have the workflow run automatically every X hours/day, so in most cases it would run without any need to update the index, but nobody would have to run it manually.
For now, keep in mind that every time the docs is updated, the docs owner needs to run the workflow manually to update the search index.
Code of Conduct
The text was updated successfully, but these errors were encountered: