- Get Started
- Functionality
- Learning
- Extension
- Dev Tooling
- APIs
- Releases
Changed on:
9 Nov 2026
`module.json`, so the CLI skipped the upload,`--skip-if-installed` skipped a plugin whose version had been reused for different code,`main` build publishes the module archive to an artifact store, either Bitbucket Downloads or your own repository, keyed by version.`trigger: manual` on the stage, and restrict who can run it in Bitbucket's deployment permissions). Agree with the client up front who approves each environment.`release/<tag>` branch. This works because every release is a tagged, reproducible build. Two caveats:1#!/bin/bash
2# cicd/verify-deploy.sh — fail unless the account carries the module version this pipeline built.
3# Usage: cicd/verify-deploy.sh <dist-dir>
4set -euo pipefail
5
6dist_dir=$1
7module_json=$(ls "$dist_dir"/*/module.json | head -n 1)
8name=$(sed -n 's/.*"name": *"\([^"]*\)".*/\1/p' "$module_json" | head -n 1)
9version=$(sed -n 's/.*"version": *"\([^"]*\)".*/\1/p' "$module_json" | head -n 1)
10
11installed=$(fluent module list --profile "$FLUENT_PROFILE")
12echo "$installed"
13
14if ! echo "$installed" | grep -E "(^|[^[:alnum:]_-])$name([^[:alnum:]_-]|$)" | grep -qF "$version"; then
15 echo "Error: $name $version is not installed on account $FLUENT_ACCOUNT_ID" >&2
16 exit 1
17fi
18echo "Verified $name $version on $FLUENT_ACCOUNT_ID"