Skip to content

Publish playbook for production #1125

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

Open
Tracked by #1631
php-coder opened this issue Sep 29, 2019 · 5 comments
Open
Tracked by #1631

Publish playbook for production #1125

php-coder opened this issue Sep 29, 2019 · 5 comments
Assignees
Labels
area/infrastructure environment/prod Issue affects only production environment
Milestone

Comments

@php-coder
Copy link
Owner

php-coder commented Sep 29, 2019

Let's commit infra/vagrant/provisioning/prod.* files to Git and use https://git-secret.io or https://github.com/AGWA/git-crypt in order to encrypt sensitive data.

Idea from @asm0dey

@php-coder php-coder added area/infrastructure environment/prod Issue affects only production environment labels Sep 29, 2019
@php-coder php-coder added this to the 0.4.2 milestone Sep 29, 2019
@php-coder php-coder self-assigned this Sep 29, 2019
@php-coder
Copy link
Owner Author

vars section should be replaced by vars_files. The external file can be encrypted then.

@php-coder
Copy link
Owner Author

@php-coder
Copy link
Owner Author

The external file can be encrypted then.

Perhaps, we can try ansible-vault: #435

@php-coder
Copy link
Owner Author

@php-coder php-coder modified the milestones: 0.4.2, next Nov 6, 2019
@php-coder
Copy link
Owner Author

Need to find a way to commit prod.inventory file as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infrastructure environment/prod Issue affects only production environment
Projects
None yet
Development

No branches or pull requests

1 participant