With minicli, Minimus customers can manage custom images as code directly from the command line. By exporting image configurations as YAML files, teams can store image recipes in version control, integrate image management into CI/CD pipelines, and automate image build workflows using the same processes they already use for application and infrastructure code.
minicli extends visibility of custom images to local terminals while giving customers the ability to create, modify, version, and build those images outside of the Minimus UI. In this blog, we'll look at how minicli works and how teams can incorporate it into their existing workflows.
minicli focuses on a set of core image management capabilities, allowing you to:
All of these functions allow you to manage custom images directly from the terminal and provide additional options for integrations into technology stacks.
I’ll now break down how each of these functions works in detail, along with their advantages.
Querying your private image repository directly from the terminal saves time by eliminating the need to switch to the Minimus UI. This makes it easy to quickly see what images exist in your custom gallery and inspect the contents of each image. From there, you can easily see image structures and compare configurations, identify differences, and determine what changes are needed for a specific build.
Understanding exactly what another team member has changed, or what modifications have been made over time, is a common challenge when managing custom images. By listing the full structure and contents of an image, minicli provides visibility inside the command line to quickly inspect and understand how an image is built.
This allows image definitions to be version-controlled, reviewed, automated, and managed alongside application and infrastructure code, so that teams can incorporate image management into the same workflows they already use to build and maintain their software and infrastructure
minicli outputs configurations in YAML format, providing a familiar, portable structure that can be reviewed, modified, and exported for use with existing version control systems.
minicli supports both exporting existing image structures and generating new template structures for users who want to build private images from scratch, making it easy to get started and to build repeatable, automated workflows.
The ability to manage YAML recipes outside of the Minimus UI gives customers greater flexibility to build on top of their images using the same automation processes already in place across their organizations. Changes such as updating packages or adding new file bundles can be made directly in the YAML file and applied by running a CLI command.
For those using Minimus File Bundle options with custom images, minicli provides visibility into the bundles that have been created and uploaded to your tenant. In addition to listing available bundles, it also shows the contents of each bundle, making it easier to understand what resources are available and which bundles you may want to include in existing or new images.
minicli builds on Minimus’s core mission: delivering secure, hardened, near vulnerability-free images while making them easy to consume and integrate across a wide range of container-based environments.
By extending image management beyond the UI, minicli enables teams to incorporate custom image builds directly into their development workflows, CI/CD pipelines, and infrastructure automation - and treat image recipes as code alongside the rest of their software stack.
.svg)
.svg)
.svg)
.svg)
