The main thing of interest here is stage-ansible.cfg and stage-ssh-config, which taken together offer a way to have an environment with different access control policies and a different VPC jumpbox without disturbing the usual case of working with your VPC production hosts. To run this, edit stage-ssh-config with a sensible jumpbox configuration and make sure the options in stage-ansible.cfg are the set of ansible options you expect to use, then invoke ansible with ANSIBLE_CONFIG like so: ``` ANSIBLE_CONFIG=stage-ansible.cfg ansible-playbook -v -i './ec2.py' edxapp_stage.yml ```
| Name |
Last commit
|
Last update |
|---|---|---|
| cloudformation_templates | Loading commit data... | |
| doc | Loading commit data... | |
| fabfile | Loading commit data... | |
| git-hooks | Loading commit data... | |
| playbooks | Loading commit data... | |
| util | Loading commit data... | |
| version-script | Loading commit data... | |
| .gitignore | Loading commit data... | |
| AUTHORS | Loading commit data... | |
| LICENSE.TXT | Loading commit data... | |
| README.md | Loading commit data... | |
| ansible-requirements.txt | Loading commit data... | |
| fabric-requirements.txt | Loading commit data... | |
| package_data.yaml | Loading commit data... |