Blog
DevOps insights, tutorials, and best practices from the Clarive team.
Plain-Text Configuration Lets an AI Assistant Work on Clarive
AI coding assistants work on text. Clarive 7.22 writes rules, resources, roles, users and groups as HCL files that name objects instead of numbering them, reports errors by file and line and shows a plan before any import. That makes an installation something an assistant can work on, with a person approving each change.
Servers, Variables and Permissions in HCL
Most of a Clarive installation is resources, projects and the roles that say who can do what. In 7.22 all of it can be written as HCL. Servers point at each other by address, variables are kept per environment, secrets have four export modes and a permission change can be reviewed like code.
An HCL View for Rules, Operations and Resources in the Clarive Interface
Clarive 7.22 brings HCL into the browser, one object at a time. A rule can be read and edited as text in the Rule Designer, a single step in its dialog, and resources, roles and user groups on their own screens. Saves go through the same engine as cla import.
Writing Clarive Rules in HCL
Clarive 7.22 writes rules as HCL. Each step becomes a nested block with a short keyword, its settings in the order its dialog shows them and nothing that was left at a default. Rules can be reviewed as diffs, searched with grep and copied between installations.
Checking a Clarive Installation Against Its Files With cla diff
cla diff compares a Clarive installation with its HCL files and exits with 1 when they disagree, the way git diff does. Together with cla import-plan and cla fmt --check, it gives a CI job what it needs to guard a configuration kept in Git.
Moving a Configuration Between Clarive Installations With cla export and cla import
A walkthrough of the two commands at the center of HCL in Clarive 7.22. cla export writes configuration into files and pulls in whatever it depends on. cla import compares those files with an installation, prints a plan and waits for a yes.
Clarive 7.22 Can Write Its Configuration as Plain Text
Clarive 7.22 writes an installation's configuration as HCL files that refer to each other by name instead of by database id. The files can be reviewed in Git and imported into another Clarive installation, from the cla command line or from new HCL views in the interface.
Deploying to Kubernetes Takes One Clarive Rule
A Clarive pipeline rule with a handful of steps deploys an application to Kubernetes. It applies the manifests with kubectl, waits for the rollout and undoes it if the new pods never come up. Project variables pick the cluster and namespace for each environment, and the whole setup is written in Clarive HCL.
A Deploy Job That Fetches Its Own Test Data
Many teams still test against a copy of production that someone restored into staging over a weekend. We move that work into the deploy job, where a step in a Clarive pipeline rule calls a Gigantics pipeline that masks and trims production data and loads it into the environment about to be tested.
Rule Execution Monitoring with Clarive Keeper
At Clarive, we're always striving to make our platform more transparent, debuggable, and user-friendly. We're excited to announce the latest update: Rule Keeper, a powerful monitoring and debugging tool that provides real-time insights into your rule...
Enhance Your Clarive Server Performance with Brotli and Gzip Compression
We’re always looking for ways to help you squeeze every bit of performance out of your Clarive instance. That’s why we now recommend enabling both Brotli and Gzip compression in your NGINX configuration. With these two working in tandem, your web ass...
SAML 2.0 Support
At Clarive, we're always striving to make our platform more secure, flexible, and user-friendly. We're excited to announce the latest update: SAML 2.0 (Security Assertion Markup Language 2.0) support. This new feature allows you to configure Single S...