This folder contains files required for gitops-style halyard

This folder contains files required for git-based Halyard updates.

1. config and default : The init script copies them to go into .hal directory of the halyard pod
2. halyard.yaml: this, along with a generic halyard-local.yaml (created by init) are copied into the /opt/halyard/config folder

Triggering the hal-deploy-apply

This is achieved with two files

1. hal-deploy-apply.yaml: This is a job with halyard image that executes hal-deploy-apply command. It essentially waits for the halyard to be ready and executes "hal apply deploy".
2. pipeline-redeploy-hal.json uses the above hal-deploy-apply.yaml and is used to create a pipeline to make the new changes effective.

USAGE

For this entire thing to work we need the following:

1. This folder
2. Dynamic accounts repo where Jenkins credentials, Kubernetes accounts & AWS credentials are stored.
3. Specify the Jenkins URL in the config file under ci.jenkins.masters.address; Jenkins credentials shall be encoded and specified in the Dynamic accounts repo.
4. OES helm chart that goes with this
5. Dynamic account git repo (https://github.com/OpsMx/gitops-accounts-sample) that exists and url fed via opsmx-gitops-secret.yaml file in oes helm chart.
6. A pipeline can be created in spinnaker using pipeline-redeploy-hal.json that shall be triggered whenever changes are made to this repo.

Info on Pipeline-promotion custom stage

Pre-requisites:

1. Git token to pull or push pipeline related information to pipelines
2. Spin CLI configuration passed as a secret
3. Configmap(pipe-promot-config-cm.yaml) to specify the behavior of pipeline promotion stage; which account to use for pipeline promotion? User email?
4. pipe-promoto-scripts-cm.yaml to mount the scripts used for carrying out pipeline promotion.

Templates to create above secrets and config maps are present in OES helm chart under templates/pipeline-promotion