https://github.com/hyperledgendary/sail-maker

Makes Resources for use with Hyperledger Fabric from Fabric's declarative descriptors
https://github.com/hyperledgendary/sail-maker

Last synced: about 1 month ago
JSON representation

Makes Resources for use with Hyperledger Fabric from Fabric's declarative descriptors

• Host: GitHub
• URL: https://github.com/hyperledgendary/sail-maker
• Owner: hyperledgendary
• License: apache-2.0
• Created: 2022-07-19T12:06:41.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2023-07-13T16:08:10.000Z (over 1 year ago)
• Last Synced: 2024-11-09T06:40:27.092Z (3 months ago)
• Language: TypeScript
• Size: 768 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# sail-maker

A Templating Tool but dialled up to 11!

Sail pulls together one or more data files (eg JSON) and then applies these through a template engine. And where this goes up to 11 is that before each template engine, you can manipulate the input data; either to make the templates themselves easier to write and maintain, transform and merge data. 

- Input formats: currently JSON and YAML (multiple of each file supported)

- Template engine: njk

- Data transformation: jsonata

The details of the templates and transaction are store in "Template Packages".

Let's say there is a single input file...xxxx.json it will be loaded and the configuration of the template package loaded. 

This configuration will supply the name of the template file and a JSONATA transformation.  Before passing the data to the template negine, it will be processed by jsonata. It's that processed data that is passed to the template engine.

## Template Package

A Template is directory with

- one or more subdirectories (only 1 level deep please) that contain the template configurations. Each containing

    - a `_cfg.yaml` file describing the configuration

    - one or more template files reference by the `_cfg.yaml`

Output path is specified on the cmd line; the output tree will match the naming of the template configuration directories

## CLI

## Example Walkthrough

- plain file copy