errose28 commented on PR #6916:
URL: https://github.com/apache/ozone/pull/6916#issuecomment-2218046023
Thanks for working on this @sarvekshayr. The PR description mentions
automation and publishing, but I don't see any automated way of running this in
the PR currently. This is important to work out because it affects the
implementation:
- If we are generating the table on every Ozone build, a Java implementation
would be preferred so no new deps are added to the build.
- If we are generating the table with GitHub actions in CI, a shell based
implementation would be preferred.
- A script using an XML parser like
[yq](https://mikefarah.gitbook.io/yq/usage/xml) (similar to jq and already
bundled in Ubuntu actions runners) or [xmllint](https://xmllint.com/) with
xpath queries can pull config keys from a config xml file.
- If we plan to run this from the [new
website](https://github.com/apache/ozone-site/tree/HDDS-9225-website-v2) in a
"pull" model for HDDS-10683, there will be no Java dependencies in that
environment.
- Note that the repo for the new website contains all the docs there
instead of having them in the ozone repo.
Since it looks like the configs require outputs from the Ozone build, not
just the source, I'm assuming the plan for automation will look something like
this:
- The Java implementation is plugged into the Maven build when the Ozone is
built.
- For the current website, the source file it generates as a result of the
build is committed back to the repo somehow, either as a separate PR by a bot
or a commit done in CI.
- For the new website, the source file it generates is committed back to the
ozone-site repo by a bot either automatically or through a pull request.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
