Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hh: deploy from the main Concourse pipeline #28

Open
cirocosta opened this issue Apr 10, 2019 · 1 comment
Open

hh: deploy from the main Concourse pipeline #28

cirocosta opened this issue Apr 10, 2019 · 1 comment

Comments

@cirocosta
Copy link
Member

cirocosta commented Apr 10, 2019

Hey,

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.

Screen Shot 2019-04-26 at 10 57 10 AM

Moving towards that, we'd need to:

  • 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.

Thanks!

@cirocosta cirocosta changed the title hh: update from the main Concourse pipeline hh: deploy from the main Concourse pipeline Apr 25, 2019
@cirocosta
Copy link
Member Author

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 😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant