We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem description (if applicable)
It would be useful to have autogenerated api documentation for the airshipctl API documents.
Proposed change
Once we are generating CRDs for all of the airshipctl API types (#574), we can use those to generate / publish api docs, similar to how we are doing this in sip and vino: https://github.com/airshipit/sip/blob/master/docs/api/sipcluster.md https://github.com/airshipit/vino/blob/master/docs/api/vino.md
Once we get the generation in place we could look at publishing airshipctl/sip/vino docs all to https://docs.airshipit.org/
The text was updated successfully, but these errors were encountered:
https://review.opendev.org/c/airship/airshipctl/+/798167
Sorry, something went wrong.
please assign to me
sanjib-35
No branches or pull requests
Problem description (if applicable)
It would be useful to have autogenerated api documentation for the airshipctl API documents.
Proposed change
Once we are generating CRDs for all of the airshipctl API types (#574), we can use those to generate / publish api docs,
similar to how we are doing this in sip and vino:
https://github.com/airshipit/sip/blob/master/docs/api/sipcluster.md
https://github.com/airshipit/vino/blob/master/docs/api/vino.md
Once we get the generation in place we could look at publishing airshipctl/sip/vino docs all to https://docs.airshipit.org/
The text was updated successfully, but these errors were encountered: