Repository navigation
docs: the module assistant is a subcommand of the core, not a shell script - #35
Merged
Merged
Conversation
…cript Manifests, catalogues, the sha256 check and the rules for what an archive may write are easier to get right and to test as Go than as shell, and the box has no jq. The command is casaos module, and nothing else of the contract changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The module contract said that the assistant is a small shell tool. It is a subcommand of the core binary instead (
casaos module list|plan|install|remove|status): the manifest and catalogue rules, the sha256 check and the rules for what an archive may write are Go code with tests, and the box has nojq. Nothing else of the contract changes. Documentation only.