In the interest of being clearer about what tools and integrations are available to use with Conjur OSS, we are drafting plans for creating a Conjur OSS Suite Release. Each suite release will detail the component versions of the Conjur server and the tools and integrations that work with it, as well as information on the new tools and features included with each release.
You can find more information on the work we’re planning in our draft design PR here:
If it’s easier, you can read up on our plans by viewing the markdown file directly here:
We’d love to hear from you if you have any thoughts about our plans! Either way, stay tuned for the first official release of the Conjur OSS Suite!
@izgerij the markdown link is broken, should be:
This file has been truncated.
# Conjur OSS Suite Release
In this effort, we intend to build a formal release process for the _Conjur OSS Suite_,
which we define as the set of components including the Conjur server, deployment utilities,
command line interface (CLI), client libraries, and integrations with platforms and DevOps tools.
At current, we have no formal process for releasing the full suite of tools in
the Conjur OSS ecosystem so that:
- It is clear to end users which version of Conjur OSS they should use, and what
integrations and tooling are compatible with that version.
- Key use cases that involve more than two components working together are automatically
tested to ensure that the end-to-end experience in those use cases works as expected.
- Development can continue on the master branch of individual components while
end users have a reliable way to pull "stable" releases for all components and
avoid unexpectedly running "edge" releases .
- It is clear what features are officially released and which are still in progress -
at current, there is no way to easily track unreleased features in our broad suite
of tools and integrations, and formally creating a system for tracking unreleased
features will help us to do a better job of comprehensively testing and releasing
Also what is the link to “repo central” ?
@boazmichaely for sharing the updated link! Next time I’ll be sure to remember to do that once the design doc is merged
People can track our progress in github at