#!/bin/bash
set -eu -o pipefail
IFS=$'\t\n'

# Enable extra repositories
dnf install -q -y epel-release
dnf config-manager --set-enabled PowerTools

# Install Python3
dnf install -q -y python3

# Install Python packages
python3 -m pip install -r /vagrant/requirements.txt

# Add host keys to `known_hosts`
mkdir -p ~/.ssh/
ssh-keyscan head >> ~/.ssh/known_hosts

#!/bin/bash
set -eu -o pipefail
IFS=$'\t\n'

# Enable extra repositories
dnf install -q -y epel-release
dnf config-manager --set-enabled PowerTools

# Install Python3
dnf install -q -y python3

# Install Python packages
python3 -m pip install -r /vagrant/requirements.txt

# Add host keys to `known_hosts`
mkdir -p ~/.ssh/
ssh-keyscan head >> ~/.ssh/known_hosts

# Add ANSIBLE_CONFIG to environment
echo "export ANSIBLE_CONFIG='/usr/local/share/Kive/dev-env/ansible.cfg'" >> /home/vagrant/.bashrc

Set ANSIBLE_CONFIG during VM provisioning
Set ANSIBLE_CONFIG during VM provisioning

This commit sets the environment variable ANSIBLE_CONFIG during
provisioning of the `dev-env` VM. This forces ansible to use the
ansible configuration in the `dev-env` directory; this directory is
globally writable (because of VirtualBox's limitations) and Ansible
won't use configuration in globally writable directories without
explicit instruction to do so.
