ogma-cli: Allow customizing the cFS application template. Refs #157.
#160
+159
−187
Conversation
This file contains 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
|
Change Manager: The functions |
…ion. Refs nasa#157. The cFS application generation backend has a fixed template that it uses to generate the cFS application. That template does not fit all use cases, so we are finding users heavily modifying the output (which is hard to keep up with when there are changes), and or not using ogma altogether for that reason. This commit modifies the ogma-core cfs command to use mustache to generate the cFS monitoring application template using variable expansion.
…n. Refs nasa#157. The cFS application generation backend has a fixed template that it uses to generate the cFS application. That template does not fit all use cases, so we are finding users heavily modifying the output (which is hard to keep up with when there are changes), and or not using ogma altogether for that reason. A recent commit introduced the ability to use mustache to expand variables in a template. This commit modifies the cfs command to accept an additional argument that points to a user-provided directory with a custom template.
…irectory to cFS app command. Refs nasa#157. The cFS application generation backend has a fixed template that it uses to generate the cFS application. That template does not fit all use cases, so we are finding users heavily modifying the output (which is hard to keep up with when there are changes), and or not using ogma altogether for that reason. A recent commit introduced into ogma-core the ability to use a custom provided template and expand variables using mustache. This commit exposes that new parameter to the user in the CLI.
…ation. Refs nasa#157. The cFS application generation backend has a fixed template that it uses to generate the cFS application. That template does not fit all use cases, so we are finding users heavily modifying the output (which is hard to keep up with when there are changes), and or not using ogma altogether for that reason. Prior commits have expanded the command to allow for customization of the template using a user-provided directory and expanding variables in the template using mustache. This commit documents the new feature in the README.
ivanperez-keera
force-pushed
the
develop-cfs-templates
branch
from
a7502b2
to
a1a9681
Compare
|
Implementor: Updates implemented, review requested. |
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.
Adjust
ogma-cliandogma-coreto allow customizing the cFS application by using custom-provided templates, as prescribed in the solution proposed for #157.