Feature, , 1 min read
Content that lives in Git
Stroom 7.11 adds Git-controlled folders, a Content Store for standard packs, and a Credentials feature to hold the secrets both of them need.
Pipelines, XSLT, dashboards and rules are code, and most teams already keep code in Git. Stroom 7.11 lets Stroom content live there too.
Git-controlled folders
You can now create a folder in Stroom that is bound to a Git repository. Everything under that folder synchronises with the repository, and you can pull changes in and push your own out. Git repos can be nested, and each one works independently of the others.
That changes how content moves between environments. Instead of exporting a zip from one instance and importing it into another, you commit to a branch and each environment pulls from it. You get a history of every change and a review step before anything reaches production.
Stroom 7.13 builds on this with HTTP and TLS configuration for Git repositories (#5675), for repositories behind a proxy or a private certificate authority.
The Content Store
The Content Store is a list of standard content items: pipelines, schemas, visualisations and so on. The list is described in files held in Git repositories. Stroom shows it in the user interface, and you choose which items to add to your instance.
Out of the box it points at the public list in gchq/stroom-content. You can add your own stores through appConfig.contentStore.urls, so an organisation can publish its own approved content to every instance it runs.
Credentials
Git needs credentials, and so do plenty of other things Stroom connects to: HTTPS endpoints, and the models behind Ask Stroom AI. The new Credentials feature gives those secrets one managed home. It can hold:
- user names and passwords
- API keys and tokens
- SSH keys
- key stores and trust stores in JKS and PKCS12 format
Where to read more
The Stroom documentation covers Git repos, the Content Store and Credentials in detail. The content packs we build for customers are delivered this way, so they arrive as a repository you own.
How it works, in detail: Docs: Content Management
Want this running on your own data? The engineers who built it can help.