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 |
|---|---|---|
| .. | ||
| edx-east | Loading commit data... | |
| edx-west | Loading commit data... | |
| files | Loading commit data... | |
| group_vars | Loading commit data... | |
| roles | Loading commit data... | |
| secure_example | Loading commit data... | |
| util | Loading commit data... | |
| vars | Loading commit data... | |
| ansible.cfg | Loading commit data... | |
| cloudformation.yml | Loading commit data... | |
| ec2.ini | Loading commit data... | |
| ec2.py | Loading commit data... | |
| edx_sandbox.yml | Loading commit data... | |
| edxapp_ref.yml | Loading commit data... | |
| edxapp_rolling_example.yml | Loading commit data... | |
| inventory.ini | Loading commit data... | |
| site.yml | Loading commit data... | |
| stage-ansible.cfg | Loading commit data... | |
| stage-ssh-config | Loading commit data... |