[INFRANG-7812] implement deploy-apps command to support slingshot deploys

[dmartschenko]

Clever Coding Standards Agreement

• Author and Review Statement, "We agree this code adheres to our Clever Global Coding Standards and other applicable Coding Standards"

JIRA

https://clever.atlassian.net/browse/INFRANG-7812

About

Add a new deploy-apps command to support slingshot deploys.

To call Slingshot directly from CircleCI using Twingate, the job needs to run on a linux machine executor not a docker executor. CircleCi docker executors do not support tunneling. However, machine executors are more expensive than docker executors, therefore rather than running the entire build/publish/deploy job on the machine executors I opted to create a new deploy-app job that can be configured to only run if the branch is master. The goal is to keep the additional cost minimal.

The vast majority of the circle-ci runs are for non-master branches so the additional cost will be applicable to a limited number of runs.

Checklist

• Increment the version number in VERSION
• Add release notes

Testing

• Created a new dev orb for deploy-apps
• Created a temp commit that allows publishes from INFRANG-7812 in this repo
• Updated do-nothing to use the orb https://github.com/Clever/do-nothing/commit/58f65b0f44fca0c24e1bfdcddc945a2f94827488
• Verified deploy-apps ran and a new artifact was created https://app.circleci.com/pipelines/github/Clever/do-nothing/268/workflows/a6ded85e-a298-42b7-bbd8-d8a4f9fdafb8/jobs/1001
• https://github.com/Clever/k8-deploys/commit/be262afbee7709935e7b0ff73e8a99590ef42a86

[andruwm]

Should these be regex strings since values can have multiple variants?

[dmartschenko]

These are templates and the app is injected into the string. From what I understand we're expecting a common structure for the config directory

[andruwm]

Yes, common config directory, but there can be multiple values.yaml. i.e., development-values.yaml