Skip to content
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

Automate testing of updatecli manifest example #188

Open
olblak opened this issue Jan 17, 2022 · 5 comments
Open

Automate testing of updatecli manifest example #188

olblak opened this issue Jan 17, 2022 · 5 comments

Comments

@olblak
Copy link
Member

olblak commented Jan 17, 2022

Summary

The current doc contains many outdated examples.
We could move all examples to dedicated yaml files and then similar to updatecli/updatecli#419, using venom to validate that example are not returning warnings.

Basic example

Include a basic example or links here.

Motivation

Better catch outdated updatecli examples

@dduportal
Copy link
Contributor

+1 with the venom proposal.

Proposal: switch documentation to be built through https://antora.org/ .

  • The venom YAML manifest could be retrieved by antora, per updatecli version, to generate correct example
  • Reference documentation would live in updatecli repository, next to the real life code/test/reference manifest and could be built standalone BUT the website would be able to use it, with versioning

@olblak
Copy link
Member Author

olblak commented Jan 19, 2022

Proposal: switch documentation to be built through https://antora.org/ .

I am not familiar with Antora so I am interested for a bootstrap discussion to see if it would help us

@dduportal
Copy link
Contributor

I'm planning to work on it after updatecli/updatecli#465. I was thinking using my forkgs of website + updatecli to provide a PoC.

Anyone interested in welcome to try as well of course!

@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added Stale and removed Stale labels Jul 22, 2022
@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Aug 22, 2022
@dduportal dduportal removed the Stale label Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants