ogma-cli: Allow customizing the standalone application template
#189
Assignees
Labels
CR:Status:Implementation
Admin only: Change request that is currently being implemented
CR:Type:Feature
Admin only: Change request pertaining to new features requested
Milestone
Comments
ivanperez-keera
added
CR:Status:Initiated
|
Change Manager: Confirmed that the issue exists. |
ivanperez-keera
added
CR:Status:Confirmed
|
Technical Lead: Confirmed that the issue should be addressed. |
ivanperez-keera
added
CR:Status:Accepted
|
Technical Lead: Issue scheduled for fixing in Ogma 1.6.0. Fix assigned to: @ivanperez-keera . |
ivanperez-keera
added
CR:Status:Scheduled
ivanperez-keera
added
CR:Status:Implementation
ivanperez-keera
added a commit
to ivanperez-keera/ogma
that referenced
this issue
Dec 11, 2024
…omponent. Refs nasa#189. The standlone backend uses a fixed template to generate the Copilot monitor. 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 standalone command to use mustache to generate the Copilot monitor via a template and variable expansion. We introduce a new template that uses variables, and we modify the cabal file to include the new files as data files that are copied over during installation. To be able to generate the files, we need to introduce a target directory option for the standalone command.
ivanperez-keera
added a commit
to ivanperez-keera/ogma
that referenced
this issue
Dec 11, 2024
…one command. Refs nasa#189.
ivanperez-keera
added a commit
to ivanperez-keera/ogma
that referenced
this issue
Dec 11, 2024
…omponent. Refs nasa#189. The standlone backend uses a fixed template to generate the Copilot monitor. 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 standalone command to use mustache to generate the Copilot monitor via a template and variable expansion. We introduce a new template that uses variables, and we modify the cabal file to include the new files as data files that are copied over during installation. To be able to generate the files, we need to introduce a target directory option for the standalone command.
ivanperez-keera
added a commit
to ivanperez-keera/ogma
that referenced
this issue
Dec 11, 2024
…one command. Refs nasa#189.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The standalone application generation backend uses a fixed template to generate the standalone 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.
Allowing users to pick their own standalone template would make Ogma more versatile.
Type
Additional context
None.
Requester
Method to check presence of bug
Not applicable (not a bug).
Expected result
Ogma allows users to pick the custom standalone application template they want to use instead of relying on the one provided by default.
Desired result
Ogma allows users to pick the custom standalone application template they want to use instead of relying on the one provided by default.
Proposed solution
Modify
ogma-coreto use variable expansion based on mustache to create the output files.Modify
ogma-core's template to use the variables used by the standalone application generation module.Modify
ogma-coreto give users the ability to pick a template directory via an optional input argument.Modify
ogma-clito give users the ability to pick a template directory via an optional input argument (exposing the corresponding argument fromogma-core).Modify
READMEto demonstrate new capability.Further notes
None.
The text was updated successfully, but these errors were encountered: