allison-analysis settings | RigFabTech docs

What allison-analysis needs from you before it installs. It goes in one small file, allison-analysis.yaml, which you pass to helm install and helm upgrade after site.yaml, as Install shows.

Starter file

allison-analysis.yaml holds every setting on this page with its description. Save it, replace each <PLACEHOLDER> and remove the optional lines you don't need. allison-analysis.schema.json describes the file to editors that check YAML against a JSON schema.

Secret settings

Passwords, keys and other values to keep private.

Name	Required	Description
`ALLISON_SUPPLIER_ID`	Yes	The supplier ID your company signs in to Allison Transmission's supplier portal with
`ALLISON_PASSWORD`	Yes	The password that goes with your supplier ID at Allison Transmission's supplier portal
`ENTRA_TENANT_ID`	Yes	Your Microsoft Entra tenant's ID
`ENTRA_CLIENT_ID`	Yes	The application (client) ID of the app registration people sign in to allison-analysis with at Microsoft Entra ID
`ENTRA_CLIENT_SECRET`	Yes	The client secret of the app registration people sign in to allison-analysis with at Microsoft Entra ID

Give them in one of two ways, never both.

In production, in a Secret of your own. A values file with passwords in it tends to end up in git, and Helm keeps a copy of the values you pass in its release record in the cluster. Write the values to a file, allison-analysis.env, one NAME=value per line with each value as it is, without quotes, then create the Secret and delete the file:

kubectl create secret generic allison-analysis-settings --namespace rft-app-allison-analysis --from-env-file=allison-analysis.env
rm allison-analysis.env

In allison-analysis.yaml, give only the Secret's name:

secrets:
  existingSecret: allison-analysis-settings

To keep the Secret in git or a secret store instead, create it with External Secrets Operator, SOPS or Sealed Secrets, with the same keys.

The Secret needs a key for every required name above. When one is missing, the product's pods don't start: kubectl --namespace rft-app-allison-analysis get pods shows CreateContainerConfigError or Init:CreateContainerConfigError, and kubectl --namespace rft-app-allison-analysis describe pods names the missing key. Add it and the pods start by themselves. After you change a value in the Secret, restart the product with kubectl --namespace rft-app-allison-analysis rollout restart deployment.

To get started, in the values file. Under secrets in allison-analysis.yaml, as the starter file has them. The chart keeps them in the Secret allison-analysis-env.

Made for you

The platform makes these once and keeps them in the Secret allison-analysis-generated. There is nothing to set.

SESSION_SECRET

In site.yaml

allison-analysis answers on allison-analysis.<domain>, under your global.rigfab.domain. To give it another name, set global.rigfab.hosts.allison-analysis to the full host name.

Check before you install

Once the base chart is installed, and before you install or upgrade this product:

rft check --chart oci://registry.rigfab.com/rft/apps/allison-analysis/charts/allison-analysis --version <VERSION> --release allison-analysis --namespace rft-app-allison-analysis --values site.yaml --values allison-analysis.yaml

It renders the chart with your files and asks the cluster whether it would accept the result, and changes nothing. A setting that is missing or misspelt in your files stops it with a message that names the setting. It doesn't look inside a Secret of your own. A misspelt name under global.rigfab is the base chart's to refuse, so check site.yaml with the base chart after every change to it, as Install shows.