The way that hush-house gets updated at the moment requires someone manually setting a version in the values.yaml file and letting the deployment happen.
Just like we update wings (whose configuration sits in https://github.com/concourse/prod) from the main pipeline, hush-house could be updated in a similar manner too.
get our secrets out of lpass, putting them into credhub (such that we can use variable interpolation for the .values.yaml file that contains our secrets).
Regarding how often to deploy: same frequency as Wings.
today we just had small trouble with the lack of automation, it'd be great to get back to this soon 😁 it's just too easy to accidentally hit the wrong make target 😁
Hey,
The way that
hush-house
gets updated at the moment requires someone manually setting a version in thevalues.yaml
file and letting the deployment happen.Just like we update
wings
(whose configuration sits in https://github.com/concourse/prod) from the main pipeline,hush-house
could be updated in a similar manner too.Moving towards that, we'd need to:
lpass
, putting them intocredhub
(such that we can use variable interpolation for the.values.yaml
file that contains our secrets).Regarding how often to deploy: same frequency as Wings.
Thanks!