kosli attest pullrequest bitbucket

Synopsis

kosli attest pullrequest bitbucket [IMAGE-NAME | FILE-PATH | DIR-PATH] [flags]

Report a Bitbucket pull request attestation to an artifact or a trail in a Kosli flow.
It checks if a pull request exists for a given merge commit and reports the pull-request attestation to Kosli. Authentication to Bitbucket can be done with an access token (recommended) or an Atlassian API token, passed via —bitbucket-username (your Atlassian account email) and —bitbucket-password. Bitbucket app passwords are no longer supported as of 28 July 2026; replace any app passwords with API tokens. Credentials need to have read access for both repos and pull requests. The attestation can be bound to a trail using the trail name. The attestation can be bound to an artifact in two ways:

using the artifact’s SHA256 fingerprint which is calculated (based on the --artifact-type flag and the artifact name/path argument) or can be provided directly (with the --fingerprint flag).
using the artifact’s name in the flow yaml template and the git commit from which the artifact is/will be created. Useful when reporting an attestation before creating/reporting the artifact.

To specify paths in a directory artifact that should always be excluded from the SHA256 calculation, you can add a .kosli_ignore file to the root of the artifact. Each line should specify a relative path or path glob to be ignored. You can include comments in this file, using #. The .kosli_ignore will be treated as part of the artifact like any other file, unless it is explicitly ignored itself.

Flags

Flag	Type	Description
`--annotate`	stringToString	[optional] Annotate the attestation with data using key=value.
`-t`, `--artifact-type`	string	The type of the artifact to calculate its SHA256 fingerprint. One of: [oci, docker, file, dir]. Only required if you want Kosli to calculate the fingerprint for you (i.e. when you don’t specify ‘`--fingerprint`’ on commands that allow it).
`--assert`	bool	[optional] Exit with non-zero code if no pull requests found for the given commit.
`--attachments`	strings	[optional] The comma-separated list of paths of attachments for the reported attestation. Attachments can be files or directories. All attachments are compressed and uploaded to Kosli’s evidence vault.
`--bitbucket-access-token`	string	Bitbucket repo/project/workspace access token. See Bitbucket access tokens for more details.
`--bitbucket-password`	string	Bitbucket API token. Bitbucket app passwords are no longer supported as of 28 July 2026. See Bitbucket authentication for more details.
`--bitbucket-username`	string	Bitbucket username (your Atlassian account email when using an API token). Only needed if you use `--bitbucket-password`
`--bitbucket-workspace`	string	Bitbucket workspace ID.
`-g`, `--commit`	string	the git merge commit to be checked for associated pull requests.
`--description`	string	[optional] attestation description
`-D`, `--dry-run`	bool	[optional] Run in dry-run mode. When enabled, no data is sent to Kosli and the CLI exits with 0 exit code regardless of any errors.
`-x`, `--exclude`	strings	[optional] The comma separated list of directories and files to exclude from fingerprinting. Can take glob patterns. Only applicable for `--artifact-type` dir.
`--external-fingerprint`	stringToString	[optional] A SHA256 fingerprint of an external attachment represented by `--external-url`. The format is label=fingerprint (labels cannot contain ’.’ or ’=’). This flag can be set multiple times. There must be an external url with a matching label for each external fingerprint.
`--external-url`	stringToString	[optional] Add labeled reference URL for an external resource. The format is label=url (labels cannot contain ’.’ or ’=’). This flag can be set multiple times. If the resource is a file or dir, you can optionally add its fingerprint via `--external-fingerprint`
`-F`, `--fingerprint`	string	[conditional] The SHA256 fingerprint of the artifact to attach the attestation to. Only required if the attestation is for an artifact and `--artifact-type` and artifact name/path are not used.
`-f`, `--flow`	string	The Kosli flow name.
`-h`, `--help`	bool	help for bitbucket
`-n`, `--name`	string	The name of the attestation as declared in the flow or trail yaml template.
`-o`, `--origin-url`	string	[optional] The url pointing to where the attestation came from or is related. (defaulted to the CI url in some CIs: docs ).
`--redact-commit-info`	strings	[optional] The list of commit info to be redacted before sending to Kosli. Allowed values are one or more of [author, message, branch].
`--registry-password`	string	[conditional] The container registry password or access token. Only required if you want to read container image SHA256 digest from a remote container registry and it is not already accessible via Docker/Podman auth files or a credential helper.
`--registry-provider`	string	[deprecated] The docker registry provider or url. Only required if you want to read docker image SHA256 digest from a remote docker registry. (DEPRECATED: no longer used)
`--registry-username`	string	[conditional] The container registry username. Only required if you want to read container image SHA256 digest from a remote container registry and it is not already accessible via Docker/Podman auth files or a credential helper.
`--repo-id`	string	[conditional] The stable, unique identifier for the repository in your VCS provider (e.g. a numeric ID). Do not use the repository name as it can change if the repo is renamed. All three of `--repo-id`, `--repo-url` and `--repository` must be set to record repository information (defaulted in some CIs: docs ).
`--repo-provider`	string	[optional] The source code hosting provider. One of: github, gitlab, bitbucket, bitbucket_cloud, bitbucket_dc, azure-devops, azure_devops_services, azure_devops_server, git, subversion (defaulted in some CIs: docs ).
`--repo-root`	string	[defaulted] The directory where the source git repository is available. Only used if `--commit` is used or defaulted in CI, see docs . (default ”.”)
`--repo-url`	string	[conditional] The URL of the repository. Must be a valid URL. All three of `--repo-id`, `--repo-url` and `--repository` must be set to record repository information (defaulted in some CIs: docs ).
`--repository`	string	[conditional] The name of the repository (e.g. owner/repo-name). All three of `--repo-id`, `--repo-url` and `--repository` must be set to record repository information (defaulted in some CIs: docs ).
`-T`, `--trail`	string	The Kosli trail name.
`-u`, `--user-data`	string	[optional] The path to a JSON file containing additional data you would like to attach to the attestation.

Flags inherited from parent commands

Flag	Type	Description
`-a`, `--api-token`	string	The Kosli API token.
`-c`, `--config-file`	string	[optional] The Kosli config file path. (default “kosli”)
`--debug`	bool	[optional] Print debug logs to stdout.
`-H`, `--host`	string	[defaulted] The Kosli endpoint. (default “https://app.kosli.com”)
`--http-proxy`	string	[optional] The HTTP proxy URL including protocol and port number. e.g. `http://proxy-server-ip:proxy-port`
`-r`, `--max-api-retries`	int	[defaulted] How many times should API calls be retried when the API host is not reachable. (default 3)
`--org`	string	The Kosli organization.
`-q`, `--quiet`	bool	[optional] Suppress non-critical warning messages. Errors and normal output are not affected. If both `--quiet` and `--debug` are set, `--debug` wins.

Examples Use Cases

These examples all assume that the flags --api-token, --org, --host, (and --flow, --trail when required), are set/provided.

report a Bitbucket pull request attestation about a pre-built docker artifact (kosli calculates the fingerprint)

kosli attest pullrequest bitbucket yourDockerImageName 
	--artifact-type docker 
	--name yourAttestationName 
	--bitbucket-access-token yourBitbucketAccessToken 
	--bitbucket-workspace yourBitbucketWorkspace 
	--commit yourArtifactGitCommit 
	--repository yourBitbucketGitRepository 

report a Bitbucket pull request attestation about a pre-built docker artifact (you provide the fingerprint)

kosli attest pullrequest bitbucket 
	--fingerprint yourDockerImageFingerprint 
	--name yourAttestationName 
	--bitbucket-access-token yourBitbucketAccessToken 
	--bitbucket-workspace yourBitbucketWorkspace 
	--commit yourArtifactGitCommit 
	--repository yourBitbucketGitRepository 

report a Bitbucket pull request attestation about a trail

kosli attest pullrequest bitbucket 
	--name yourAttestationName 
	--bitbucket-access-token yourBitbucketAccessToken 
	--bitbucket-workspace yourBitbucketWorkspace 
	--commit yourArtifactGitCommit 
	--repository yourBitbucketGitRepository 

report a Bitbucket pull request attestation about an artifact which has not been reported yet in a trail

kosli attest pullrequest bitbucket 
	--name yourTemplateArtifactName.yourAttestationName 
	--bitbucket-access-token yourBitbucketAccessToken 
	--bitbucket-workspace yourBitbucketWorkspace 
	--commit yourArtifactGitCommit 
	--repository yourBitbucketGitRepository 

report a Bitbucket pull request attestation about a trail with an attachment

kosli attest pullrequest bitbucket 
	--name yourAttestationName 
	--bitbucket-access-token yourBitbucketAccessToken 
	--bitbucket-workspace yourBitbucketWorkspace 
	--commit yourArtifactGitCommit 
	--repository yourBitbucketGitRepository 
	--attachments=yourAttachmentPathName 

fail if a pull request does not exist for your artifact

kosli attest pullrequest bitbucket 
	--name yourTemplateArtifactName.yourAttestationName 
	--bitbucket-access-token yourBitbucketAccessToken 
	--bitbucket-workspace yourBitbucketWorkspace 
	--commit yourArtifactGitCommit 
	--repository yourBitbucketGitRepository 
	--assert

General

Top-level commands

kosli allow

kosli archive

kosli assert

kosli attest

kosli begin

kosli create

kosli delete

kosli diff

kosli disable / enable

kosli evaluate

kosli get

kosli join

kosli list

kosli log

kosli rename

kosli report

kosli rotate

kosli snapshot

kosli unarchive

kosli update

kosli attest pullrequest bitbucket

Synopsis

Flags

Flags inherited from parent commands

Examples Use Cases

​Synopsis

​Flags

​Flags inherited from parent commands

​Examples Use Cases

Synopsis

Flags

Flags inherited from parent commands

Examples Use Cases