feat: split tools

[jkowalleck]

fixes #67

• a new tool.schema.json was created
• the tools.json was split into individual files in the tools/ folder
• each file in the tools/ folder follows the new tool.schema.json
• added automated validators for the files in the tools/ folder
• added automated processes that assemble the tools.json based on all files in the tools/ folder
• modified the metaconfigurator config and links to easy file modifications
• created helpers to split and assemble the tools.json

result:

• we still maintain the tools.json file
• we have separate files for each tool, so that it is easy to add/modify tools in parallel

[jkowalleck]

preview:
https://www.metaconfigurator.org?schema=https://raw.githubusercontent.com/CycloneDX/tool-center/refs/heads/feat/devide-tools/schemas/tool.schema.json&settings=https://raw.githubusercontent.com/CycloneDX/tool-center/refs/heads/feat/devide-tools/metaConfiguratorSettings.json

[stevespringett]

Overall I think this looks good. However, we may need to change where the Cloudflare Hook is executed. The idea is that whenever tools.json is updated, it will rebuild the public website. That process is now handled in assemble_tools_json.yml.

[stevespringett]

I think we may need to trigger Cloudflare Deploy hook iin the assemble_tools_json.yml instead.

[jkowalleck]

we have a cloudflare deploy hook in the docs - what does it actually do?

for the changes in tools.json - i would go with a scheduled task for this purpose.
this can be added in a different pullrequest.

PS:

• see feat: publish once an hour #72

[stevespringett]

we have a cloudflare deploy hook in the docs - what does it actually do?

It triggers Cloudflare pages to checkout the website repo and tools.json and rebuild and redeploy the entire website. A scheduled task should be avoided as it will erroneously result in timestamps in sitemap.xml for a "changed" website when there were no actual changes made. I don't know if there are any SEO penalties for this or not, but I'd rather not find out.

[jkowalleck]

understood.
the publication is triggered via .github/workflows/publish_toolcenter.yml now .