#!/usr/bin/env bash
# jetstack/cert-manager v1.21.0 - base variant: default
# Path: fetch this entry's retained objects, check their SHA-256, then apply
# them with kubectl. It uses curl, shasum, awk and kubectl. It needs no cub
# CLI and no ConfigHub account.
# Generated by scripts/generate-public-site.mjs from this entry's listing:
# https://confighub.github.io/helm-expt/site/listings/jetstack-cert-manager-v1-21-0-default.json
# Entry page: https://confighub.github.io/helm-expt/site/charts/jetstack-cert-manager-v1-21-0.html
set -euo pipefail

say() { printf '\n>> %s\n' "$*"; }

for tool in curl awk kubectl; do
  if ! command -v "$tool" >/dev/null 2>&1; then
    printf '%s is required and was not found.\n' "$tool" >&2
    exit 1
  fi
done
if command -v shasum >/dev/null 2>&1; then
  sha256_of() { shasum -a 256 "$1" | awk '{print $1}'; }
elif command -v sha256sum >/dev/null 2>&1; then
  sha256_of() { sha256sum "$1" | awk '{print $1}'; }
else
  printf 'shasum is required and was not found.\n' >&2
  exit 1
fi

work=./jetstack-cert-manager-v1-21-0-default-objects
objects_url=https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/jetstack/cert-manager/v1.21.0/revisions/default/r001/rendered/release-objects.yaml
objects_sha256=9e9b6442f769b8a02974ae801946207452f7f4990e873e007e4d32ec88d9cc09

say "Fetch the retained objects into $work/objects.yaml"
mkdir -p "$work"
curl -fsSL -o "$work/objects.yaml" "$objects_url"

say "Check the file against the SHA-256 in the listing"
fetched_sha256="$(sha256_of "$work/objects.yaml")"
if [ "$fetched_sha256" != "$objects_sha256" ]; then
  printf 'The file differs from the listing, so the script stops. Nothing was applied.\n  listing: %s\n  fetched: %s\n' "$objects_sha256" "$fetched_sha256" >&2
  exit 1
fi
printf 'The file matches: sha256 %s\n' "$fetched_sha256"

say "Split the file into its 40 objects. The cluster is untouched so far"
rm -rf "$work/docs" "$work/rest"
mkdir -p "$work/docs" "$work/rest"
awk -v dir="$work/docs" 'BEGIN { n = 0; f = sprintf("%s/doc-%04d.yaml", dir, n) } /^---[ \t]*$/ { close(f); n++; f = sprintf("%s/doc-%04d.yaml", dir, n); next } { print > f }' "$work/objects.yaml"
for n in 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012; do mv "$work/docs/doc-$n.yaml" "$work/rest/"; done
for n in 0013 0014 0015 0016 0017 0018 0019 0020 0021 0022 0023 0024; do mv "$work/docs/doc-$n.yaml" "$work/rest/"; done
for n in 0025 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036; do mv "$work/docs/doc-$n.yaml" "$work/rest/"; done
for n in 0037 0038 0039 0040; do mv "$work/docs/doc-$n.yaml" "$work/rest/"; done
ls "$work/rest"

if [ "${REQUIREMENTS_READY:-0}" != "1" ]; then
  say "Stop before applying anything. This entry's plan has 2 steps that an install needs first"
  cat >&2 <<'EOF_REQUIREMENTS'
This script cannot carry out these steps of the plan. They are yours to do, with your own values:
  - 6 CRDs must exist before apply. cert-manager CRD staged before the default chart and its startup API check.
  - The chart defines 4 hook object(s) that do not travel in a flattened bundle, so the work they do has to happen some other way. A recorded run installed this base without them and watched that work happen as the ordered actions below. The listing gives the rest.
Nothing was applied. Complete them before you apply the objects.
When they are done, re-run with:
  REQUIREMENTS_READY=1 bash try-objects.sh
EOF_REQUIREMENTS
  exit 1
fi
say "REQUIREMENTS_READY=1 is set. The script takes your word for 2 steps and does not check them"

say "Check that kubectl reaches a cluster"
if ! kubectl get --raw /version >/dev/null 2>&1; then
  printf 'kubectl cannot reach a cluster. Point it at a throwaway cluster and re-run this script.\n' >&2
  exit 1
fi
kubectl config current-context 2>/dev/null || true

say "Create the cert-manager namespace if it does not exist"
if ! kubectl get namespace cert-manager >/dev/null 2>&1; then
  kubectl create namespace cert-manager
fi

say "Create the kube-system namespace if it does not exist"
if ! kubectl get namespace kube-system >/dev/null 2>&1; then
  kubectl create namespace kube-system
fi

say "Apply the 40 objects"
kubectl apply -f "$work/rest"

say "Done. kubectl applied the 40 objects of this entry's retained file."
say "The script stops here. It did not wait for any workload to start"
say "Not run by this script: 2 steps of this entry's plan. The entry page says who runs each one."
cat <<'EOF_NOT_RUN'
   - 6 CRDs must exist before apply. cert-manager CRD staged before the default chart and its startup API check.
   - The chart defines 4 hook object(s) that do not travel in a flattened bundle, so the work they do has to happen some other way. A recorded run installed this base without them and watched that work happen as the ordered actions below. The listing gives the rest.
EOF_NOT_RUN