Name |
Last commit
|
Last update |
---|---|---|
cloud_migrations | ||
cloudformation_templates | ||
doc | ||
git-hooks | ||
playbooks | ||
util | ||
vagrant | ||
.gitignore | ||
.travis.yml | ||
AUTHORS | ||
CHANGELOG.md | ||
LICENSE.TXT | ||
README.md | ||
requirements.txt |
Having `--tags deploy` be part of the ansible-playbook call that `/edx/bin/update` makes is not intuitive. It's broken us a few times recently and I don't think the benefit it provides is worth the cost and confusion. I feel that anyone who wants to use tags will know how to do it without using `/edx/bin/update`.
Name |
Last commit
|
Last update |
---|---|---|
cloud_migrations | Loading commit data... | |
cloudformation_templates | Loading commit data... | |
doc | Loading commit data... | |
git-hooks | Loading commit data... | |
playbooks | Loading commit data... | |
util | Loading commit data... | |
vagrant | Loading commit data... | |
.gitignore | Loading commit data... | |
.travis.yml | Loading commit data... | |
AUTHORS | Loading commit data... | |
CHANGELOG.md | Loading commit data... | |
LICENSE.TXT | Loading commit data... | |
README.md | Loading commit data... | |
requirements.txt | Loading commit data... |