-
Notifications
You must be signed in to change notification settings - Fork 15
Introduce common reference section #483
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
Conversation
- Create index page for CRDs with title and description. - Add detailed documentation for ComponentVersion CRD including examples and specifications. - Create index page for OCM Controller with title and description. - Document the architecture of the OCM Controller, detailing its functions and sub-controllers. - Create reference index page for OCM CLI and OCM Controller documentation. On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
✅ Deploy Preview for open-component-model ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…ation commands, and update links in the documentation generation scripts to reflect the new structure under /docs/reference/ocm-cli. This includes the removal of files related to common transport archives, component archives, component versions, and verification processes, as well as adjustments to the mapping of commands to their respective documentation URLs. On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
- Introduced a comprehensive architecture document for the OCM Kubernetes Controllers, detailing their functions, components, and interactions. - Created a new section for Custom Resource Definitions (CRDs) with an overview and examples. - Added detailed documentation for the ComponentVersion CRD, including specifications, examples, and debugging information. On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
…gle layout templates On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
- Created documentation for the `ocm sign` command, including subcommands for signing component versions and hashes. - Added detailed options and usage examples for the `ocm sign componentversions` and `ocm sign hash` commands. - Introduced the `ocm transfer` command documentation, covering the transfer of OCI artifacts, common transport archives, and component versions. - Documented options and examples for `ocm transfer artifacts`, `ocm transfer commontransportarchive`, and `ocm transfer componentversions`. - Added verification command documentation with a focus on verifying component version signatures using the `ocm verify` command. - Included detailed descriptions, options, and examples for `ocm verify componentversions`. On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
…ation On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
…rence-section On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
…rence-section On-behalf-of: Gerald Morrison (SAP) <[email protected]> Signed-off-by: Gerald Morrison (SAP) <[email protected]>
@jakobmoellerdev, the PR can be reviewed. I resolved all conflicts after the latest changes. The PR can be checked in the Netlify deploy view. The changes to the Gh action "Update CLI docs" can only be correctly tested, once a new PR after the next v12 release is done and triggers the action. |
Looks alright. I run the code generation and locally also run the website. Looks alright. |
What this PR does / why we need it
Replace dedicated reference sections and merge into one with sub-folders