Porter enables you to package your application artifact, client tools, configuration and deployment logic together as an installer that you can distribute, and install with a single command.
PR #2897 moved the CLI reference file, but the CLI reference generation still points to the old location. That also means that the CLI reference haven't be updated since except for manual changes.
Notes for the reviewer
The structure of the CLI reference documentation will change a little, the "folder" structure will disappear. That is a downside, but compared to having the CLI reference up-to-date, I think it is fine.
If we want to have a folder structure, it could be implemented in a different PR, as it requires a greater amount of changes to the CLI reference docs generation
CurrentNew
Checklist
[ ] Did you write tests?
[ ] Did you write documentation?
[ ] Did you change porter.yaml or a storage document record? Update the corresponding schema file.
[ ] If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇♀️
What does this change
PR #2897 moved the CLI reference file, but the CLI reference generation still points to the old location. That also means that the CLI reference haven't be updated since except for manual changes.
Notes for the reviewer
The structure of the CLI reference documentation will change a little, the "folder" structure will disappear. That is a downside, but compared to having the CLI reference up-to-date, I think it is fine. If we want to have a folder structure, it could be implemented in a different PR, as it requires a greater amount of changes to the CLI reference docs generation
Current
New
Checklist