Skip to content

Add new configuration to set up safegraph deployment branch #182

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

Merged
merged 72 commits into from
Aug 5, 2020

Conversation

korlaxxalrok
Copy link
Contributor

No description provided.

Jingjing Tang and others added 26 commits July 17, 2020 08:55
- Add new google_health Jenkins pipeline stage scripts
- Add the abilty for Ansible to write either a file or a template
  depending on which has been configured for the indicator
- Add Ansible template directory (special tall bookshelf)
- Add the ability to keep sensitive variables in `vault.yaml`
- Add google_health production params template

Encrypt vault.yaml
- Add: Ansible playbook for securely handling placing the
  `params.json` template we need for testing. This will happen during
  the Jenkins build stage when we are setting up the venv in the
  workspace on the Jenkins server.
- Add: Test `params.json` template.
- Add: Jenkins user variable.
- Fix: Was incorrectly trying to use a file instead of a template in
  `ansible-deploy.yaml`.
- Add: Call the small Ansible playbook from the Jenkins build wrapper.
…raph

- Add Jenkins/Ansible deployment changes
and Automation
- Add Jenkins pipeline scripts
- Add production params template
- Update vars and vault files with AWS secrets
@krivard
Copy link
Contributor

krivard commented Aug 5, 2020

If the listing errors are easy to fix, do so; if they're more involved, disable the affected checks.

@korlaxxalrok korlaxxalrok merged commit 2fd5c72 into deploy-safegraph Aug 5, 2020
@korlaxxalrok korlaxxalrok deleted the build-deploy-safegraph branch August 5, 2020 19:39
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

Successfully merging this pull request may close these issues.

3 participants