You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
DevOps-Bash-tools/jenkins/jenkins_cred_set_secret_fil...

97 lines
3.3 KiB
Bash

#!/usr/bin/env bash
# vim:ts=4:sts=4:sw=4:et
# args: hari-test-api-secret-file ~/.aws/keys/circleci_accessKeys.csv "" "" "My Secret File"
#
# Author: Hari Sekhon
# Date: 2022-06-28 18:34:34 +0100 (Tue, 28 Jun 2022)
#
# https://github.com/HariSekhon/DevOps-Bash-tools
#
# License: see accompanying Hari Sekhon LICENSE file
#
# If you're using my code you're welcome to connect with me on LinkedIn and optionally send me feedback to help steer this or other code I publish
#
# https://www.linkedin.com/in/HariSekhon
#
# https://github.com/jenkinsci/credentials-plugin/blob/master/docs/user.adoc#creating-a-credentials
set -euo pipefail
[ -n "${DEBUG:-}" ] && set -x
srcdir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
# shellcheck disable=SC1090,SC1091
. "$srcdir/lib/utils.sh"
# shellcheck disable=SC2034,SC2154
usage_description="
Creates or Updates a Jenkins Secret File Credential in the given credential store and domain
Defaults to the 'system' provider's store and global domain '_'
If credential id and secret file aren't given as arguments, then reads from stdin, reading in KEY=VALUE
or standard shell export format - useful for shell piping
In cases where you are reading secrets from stdin, you can set the store and domain via the environment variables
\$JENKINS_SECRET_STORE and \$JENKINS_SECRET_DOMAIN
Tested on Jenkins 2.319 with Credentials plugin 2.5
Uses the adjacent jenkins_api.sh - see there for authentication details
Examples:
# create a credential with id 'aws-access-key-csv', and file ~/.aws/keys/jenkins_accessKeys.csv:
${0##*/} aws-access-key-csv ~/.aws/keys/jenkins_accessKeys.csv
# with a description, leaving the store and domain as the default global one:
${0##*/} aws-access-key-csv ~/.aws/keys/jenkins_accessKeys.csv '' '' 'My AWS Access Key CSV'
# or piped from standard input:
# export JENKINS_SECRET_STORE and JENKINS_SECRET_DOMAIN if using stdin but not using system global store
echo aws-access-key-csv=~/.aws/keys/jenkins_accessKeys.csv | ${0##*/}
"
# used by usage() in lib/utils.sh
# shellcheck disable=SC2034
usage_args="[<credential_id> <secret_file> <store> <domain> <description> <curl_options>]"
help_usage "$@"
id="${1:-}"
secret_file="${2:-}"
store="${3:-${JENKINS_SECRET_STORE:-system}}"
domain="${4:-${JENKINS_SECRET_DOMAIN:-_}}"
description="${5:-}"
for _ in {1..5}; do shift || : ; done
curl_args=("$@")
set_credential(){
local key_value="$1"
local description="${2:-}"
parse_export_key_value "$key_value"
# key/value are exported by above function
# shellcheck disable=SC2154
local id="$key"
# shellcheck disable=SC2154
local secret="$value"
if "$srcdir/jenkins_cred_get.sh" "$id" "$store" "$domain" &>/dev/null; then
"$srcdir/jenkins_cred_update_secret_file.sh" "$id" "$secret" "$store" "$domain" "$description" ${curl_args:+"${curl_args[@]}"}
else
"$srcdir/jenkins_cred_add_secret_file.sh" "$id" "$secret" "$store" "$domain" "$description" ${curl_args:+"${curl_args[@]}"}
fi
}
if [ -n "$secret_file" ]; then
set_credential "$id"="$secret_file" "$description"
else
while read -r id_secretFile description; do
set_credential "$id_secretFile" "$description"
done < <(sed 's/^[[:space:]]*export[[:space:]]*//; /^[[:space:]]*$/d')
fi