2 min read
It is now possible to authenticate to Bitbucket using access tokens.
As of CLI v2.11.10, CLI commands that communicate with Bitbucket can use the `- -bitbucket-access-token` flag to authenticate with Bitbucket instead of the user-tied app passwords. This ensures that your CI pipelines don’t break if users leave.
App rebrand
Kosli has introduced a new brand alongside an updated version of www.kosli.com. As part of this evolution, our app has been refreshed with a polished new look, featuring updated colors and a brand-new logo.
Targeting Specific Jira Projects with Project Key Filtering
We’ve enhanced the kosli attest jira command with a new --jira-project-key flag that allows you to specify which Jira project keys should be matched when searching for ticket references. This solves an issue where text that resembles a Jira ticket ID (but isn’t from your relevant project) could be incorrectly identified and fail compliance checks.
For example, references like “SD-123” from a Service Desk system might be mistakenly treated as Jira tickets. With this new flag, you can ensure that only tickets from specified projects are considered during attestation:
$ kosli attest jira ARTIFACT --jira-project-key=OPS
You can specify multiple project keys if needed:
$ kosli attest jira ARTIFACT --jira-project-key=OPS --jira-project-key=DEV
This enhancement gives you greater control over your compliance requirements while reducing false negatives in your attestation process.
