Package Exports
- hlambda-cli
- hlambda-cli/src/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (hlambda-cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
hlambda-cli 
hlambda-cli - CLI tool for managing hlambda server.
Installation
npm
$ npm install -g hlambda-cliExample
First you will need to get hlambda server running, either in docker or locally.
$ hlambda --version$ hlambda init my-first-hlambda-app$ cd my-first-hlambda-appChange the admin_secret in the config.yaml manually or just run
$ hlambda config save --admin-secret "demo"this will edit the config.yaml file and save admin secret value in that file (please take extra care when commiting config.yaml file to not leak secrets)
You can then export the existing metadata from the running server use
$ hlambda metadata exportor you can apply the changes by running
$ hlambda metadata applyor run the hlambda metadata apply with option --admin-secret
$ hlambda metadata apply --admin-secret <your_secret>to export existing data from the hlambda server run
$ hlambda metadata export --admin-secret <your_secret>Reloading metadata
By default metadata apply should also automatically reload the metadata on the server unless --no-auto-reload option is set
$ hlambda metadata apply --no-auto-reloadto do it manually you can run:
$ hlambda metadata reloadClearing metadata
If you want to clear all the metadata from the server
$ hlambda metadata clear