Security News
JSR Working Group Kicks Off with Ambitious Roadmap and Plans for Open Governance
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
@lifeomic/cli
Advanced tools
This command line interface provides functionality offered by LifeOmic's Precision Health Cloud APIs inside an interactive terminal or in a scripted environment.
Install via npm
or yarn
:
npm install -g @lifeomic/cli
yarn global add @lifeomic/cli
or you can download and install the binary from the latest release.
Run lo setup
to configure the default environment and account you wish to use.
You can later override the default account using the -a
option for commands.
Use lo auth
to obtain access credentials when using username / password
authentication. A browser will be opened and you can enter your credentials in
the LifeOmic login view.
You can also use the client credentials grant flow for obtaining access tokens.
To do this, create a custom authentication client
here and be sure to
select the Client credentials
flow under the Allowed OAuth Flows
section.
Run lo setup
again and choose Y
to use a custom authentication client and
enter the client ID and secret and then choose Y
again to use client
credentials for authentication. Note that for this option, you do not need to
run lo auth
as username and password credentials are not used for this
credentials grant.
You can also provide an API key or access and refresh tokens in
the PHC_ACCESS_TOKEN
and PHC_REFRESH_TOKEN
environment variables. With these
set, you can bypass using lo auth
.
To use an API key for authentication, follow the
Set Up API Keys
instructions to create the key. You can also use the command lo api-keys-create
.
Be sure to capture the value of the API key when it is created as you will not
be able to retrieve the value after the first attempt. Run lo setup
and choose
'Y' to use an API key and provide the API key value.
If you wish to use SSO, then you need to create a custom authentication client
here and configure
your SAML 2.0 identity provider. For the callback URL on the authentication
client, be sure to add http://localhost:8787
. Then run lo setup
again and
choose 'Y' to use a custom authentication client and provide the client ID and
secret (if a private client was created). When running lo auth
again, a
browser should open and be redirected to the identity provider being used for
SSO.
lo <command> [options]
lo
offers many commands and those can be displayed by using the -h / --help
command line option. For example:
❯ lo --help
Usage: lo <command> [options]
Options:
-V, --version output the version number
-h, --help output usage information
Commands:
accounts [options] List accounts
accounts-get [options] <account> Fetch an account
...
</abbreviated>
Get help for a specific command:
❯ lo <command> --help
❯ lo tasks --help
Usage: tasks [options] <datasetId>
List tasks
Options:
-a, --account <account> Override the default LifeOmic account
--json Print output as JSON
--prefix <prefix> Filter tasks where the name begins with a prefix
--state <state> Filter tasks by state
--view <view> Specify MINIMAL to just get task state
--page-size <pageSize> Number of items to return (default: 25)
--next-page-token <nextPageToken> Next page token
-h, --help output usage information
We encourage public contributions! Please review CONTRIBUTING.md and CODE_OF_CONDUCT.md for details on our code of conduct and development process.
This project is hosted on GitHub. You can clone this project directly using this command:
git clone git@github.com:lifeomic/cli.git
Run tests with npm
or yarn
:
npm test
yarn test
Releases are created by making a PR, incrementing the version in package.json
, merging the PR,
and then finally tagging master with a tag like v4.5.3
.
Packages for each release are published to npm. See CHANGELOG.md for release notes.
This project uses Semantic Versioning.
This project is licensed under the MIT License - see LICENSE file for details.
See the list of contributors who participate in this project.
This project is built with the following:
FAQs
CLI for interacting with the LifeOmic PHC API.
We found that @lifeomic/cli demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.