6 posts tagged with "cli"

Overview​

We've added a new skpr console command to the Skpr CLI that lets you directly access the Skpr Console for an environment.

Example​

skpr console <environment>

Link​

• v1.9.0

Overview​

We've added a new skpr logs query command to the Skpr CLI that lets you run a bounded query over the logs of a running application.

Unlike the streaming skpr logs tail command, skpr logs query fetches a finite window of log events - making it ideal for investigating past incidents, filtering for specific errors, or reviewing activity over a defined time period.

For more information, run:

skpr logs query --help

Link​

• v1.9.0

Overview​

We've introduced improvements to how skpr validate and skpr deploy handle warnings.

These changes are designed to surface issues early, particularly in CI workflows, before they make it into a deployment.

Changes​

Validate now exits with an error on warnings​

Previously, running skpr validate <env> would exit successfully even if your site had warnings. As of v1.9.0, warnings will cause the command to exit with a non-zero status, making it easier to catch issues early in CI pipelines.

skpr validate dev

Deploy blocks on warnings​

If your site has warnings, skpr deploy <env> will now throw an error and refuse to deploy. Violations and warnings will be printed on failure so you can see exactly what needs to be addressed.

skpr deploy dev

Bypassing warnings​

If you've reviewed the warnings and are happy to proceed, you can bypass them using the --ignore-warnings flag:

skpr deploy dev --ignore-warnings

Note: Violations cannot be bypassed — only warnings.

What triggers a warning?​

Warnings are raised for significant configuration changes, such as removing a domain name from an environment. The set of conditions that trigger warnings will be updated with each Skpr minor release as required.

Link​

• v1.9.0

Overview​

In release v1.5.0, we've added a new command to the Skpr command-line interface (CLI): release pull.

This command pulls the packaged container images created by the skpr package command, so development teams can pull and debug the packaged application artefacts directly. To use it, run:

$ skpr release pull <environment>

Link​

• v1.5.0

Overview​

We’re excited to announce the v1.0.0 release of the Skpr CLI, a major milestone in the project’s journey.

Representing the culmination of years of work, this version lays the groundwork for continued improvement and collaboration in our public GitHub repository.

github.com/skpr/cli

Highlights​

• New CLI Framework: Built on Cobra for a more consistent and intuitive command experience.
• Improved Styling: A refreshed, colourful help screen now welcomes you with clear examples and neatly grouped commands for easier navigation.
• Open Source: Fully available and maintained on GitHub.
• API Integration: Connected with our new open-source API definition — skpr/api.

Upgrading​

Skpr CLI v1.0.0 is available through all existing upgrade paths. Follow the installation or upgrade instructions here:

docs.skpr.io/install

Overview​

The Skpr command line interface (CLI) is now more resilient during backup and restore operations, even in challenging conditions such as:

• Connectivity interruptions
• Cluster upgrades

To prevent transient errors from causing CI/CD pipeline failures, the CLI now features a retry and backoff mechanism that maintains stability throughout these processes.