npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@opsera/opsera-cli

v0.1.4

Published

Command Line Processor (opsera-cli) helps customer to invoke OpsEra services through command line interface. This OpsEra CLI gives support for Creating, Executing OpsEra pipelines from customer’s local machine using YAML. Customers can download OpsEra CLI

Downloads

9

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

opsera_srinivasanopsera_srinivasanopserasupportopserasupportsundarrajanrsundarrajanrnawaz1001nawaz1001

Keywords

opseracliDevOpsCICD

Readme

Opsera Command Line

Opsera Inc

N|Solid

Description

Opsera Command Line (opsera-cli) helps customer to invoke Opsera services through command line interface. This Opsera CLI provides support for Creating, Executing Opsera pipelines from customer’s local machine using YAML. Users can download Opsera CLI and able to install it in their local just by hitting simple npm command

Prerequisites

Node should be installed on the User's machine to pull Opsera CLI from NPM repository.

User has to run the below command to get this installation done.

npm i @opsera/opsera-cli -g

Commands

Commands that are available as part of opsera-cli listed below. Also, the user can hit help command to know all possible commands and its arguments.

opsera -h
opsera --help

Configure

opsera configure

Get Pipelines

opsera get pipelines
opsera get pipelines --out=<fileName>
opsera get pipelines --out <fileName>
opsera get pipelines -o=<fileName>
opsera get pipelines -o <fileName>
opsera get pipelines >> <fileName>

Get Tools

opsera get tools
opsera get tools --out=<fileName>
opsera get tools -o=<fileName>
opsera get tools >> <fileName>

Run Pipeline

opsera run pipeline --pipeline-id=<pipelineId>
opsera run pipeline -p=<pipelineId>

Stop Pipeline

opsera stop pipeline --pipeline-id=<pipelineId>

Status Pipeline

opsera status pipeline --pipeline-id=<pipelineId>
opsera status pipeline --pipeline-id=<pipelineId> --run-count=<runCount>
opsera status pipeline -p=<pipelineId>
opsera status pipeline -p=<pipelineId> -c=<runCount>

Reset Pipeline

opsera reset pipeline --pipeline-id=<pipelineId>

Summary

opsera summary pipeline --pipeline-id=<pipelineId>
opsera summary pipeline --pipeline-id=<pipelineId> --out=<fileName>
opsera summary tool --tool-id=<toolId>
opsera summary tool --tool-id=<toolId> --out=<fileName>

Logs

opsera logs pipeline --pipeline-id=<pipelineId>
opsera logs pipeline --pipeline-id=<pipelineId> --run-count=<runCount>
opsera logs pipeline --pipeline-id=<pipelineId> --run-count=<runCount> --out=<fileName>