-
Notifications
You must be signed in to change notification settings - Fork 154
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
Update method in which external content is ingested. #93
Comments
this is a long term replacement and is not needed for the contributor site. |
/assign @markyjackson-taulia |
Hey @markyjackson-taulia! I had started poking at this issue a couple weeks ago to see what we needed. I'm pretty sure a simple include will work with a bit of tweaking. Did you want to see what I had in draft form? |
@nimbinatus sorry for the delay in responding. I would be interested to see what you have. I am thinking of converting this in its entirety to go so I can include some testing around it. |
@markyjackson-taulia sounds good! I'll try to clean up my code with some comments and get my branch up this week for you to poke at. |
@markyjackson-taulia here's what I was poking at. It does require a bit more work to add pages to the repo, and it's not 100% accurate yet regarding some of the internal links on each page. However, it's more native to Hugo, so I was hoping it would be a bit cleaner to test. |
Will run some test |
The hardest part that I'm concerned about with the hugo method is the replication of the link expander. It determines if the content is has been synced locally and updates it with the correct path, or if not -- expand it to the full github url. This blurb is slightly out of date (updated in #110), but it is similar enough to explain. |
I found that through my testing, using the hugo method did not do fully what I wanted so I am going to redo this. Thank you @nimbinatus for the code |
/milestone v1.19 |
@nimbinatus I started the work in the above PR, did it in python but there is still more to do. |
We are going to scrap this python code and move toward go after discussing with @mrbobbytables |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/lifecycle frozen |
Hi All, I would like to collaborate on this! Let me know what is the status of the same 😄 |
It got put on the back-burner and hasn't really made any progress^^;;; The configs right now are just some CSVs, but ideally we'd switch to a yaml spec - something like:
Using the community repo csv as an example:
Sorta like rsync syntax. |
/help |
1 similar comment
/help |
@mrbobbytables: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@mrbobbytables Will ansible work in this case? https://docs.ansible.com/ansible/latest/collections/ansible/posix/synchronize_module.html |
@whs-dot-hk No, this would be best in golang where it could use the same library used by Hugo to generate links. The difficult part is not syncing the content, it's ensuring all links within the pages are updated without potentially modifying other content like code snippets in code fences. |
@mrbobbytables Should it be a separate go program or a hugo "plugin"? |
@whs-dot-hk it would be a separate program. |
/assign |
/assign |
Currently, external content is brought into the contributor-site via the hack/gen-content.sh bash script. In its original inception, it was quite small and lean -- but as a bash script usually does, it has grown to be unwieldy.
It'd be far better to replace it with a more supportable (and testable) means of bringing in external content. This means rewriting it something like go or python, or finding some other means of bringing in external content.
/kind feature
cc @vishakhanihore @nimbinatus
The text was updated successfully, but these errors were encountered: