From the course: Ansible: From Basics to Guru by Pearson

Unlock this course with a free trial

Join today to access over 25,200 courses taught by industry experts.

Working with ansible-navigator

Working with ansible-navigator

All right, let's check out how you can work with Ansible Navigator. So first you need to take care of some settings. If you don't, you will always need to provide them on the command line, and that is so inconvenient. Settings for Ansible Navigator can be specified in a configuration file. You can define a generic configuration file in your home directory. Call it .ansible-navigator.yaml in that case. As an alternative, you can use ansible-navigator.yaml file in the current project directory. And that will always have a higher priority. That's how it always works in Ansible. More specific, has a higher priority. Now here's a couple of recommended settings. First I recommend you set pull policy to missing. Because if you don't, Ansible Navigator, every time you start it, will check if a newer version of the container image is available and that takes too much time. So that's a useless option. This is why you need pull policy missing. Playbook artifact enable false is also something…

Contents