• AnsibleFest
  • Products
  • Community
  • Webinars & Training
  • Blog
Ansible Logo
Documentation
Ansible
7

Ansible getting started

  • Getting started with Ansible

Installation, Upgrade & Configuration

  • Installation Guide
  • Ansible Porting Guides

Using Ansible

  • Building Ansible inventories
  • Using Ansible command line tools
  • Using Ansible playbooks
  • Protecting sensitive data with Ansible vault
  • Using Ansible modules and plugins
  • Using Ansible collections
  • Using Ansible on Windows and BSD
  • Ansible tips and tricks

Contributing to Ansible

  • Ansible Community Guide
  • Ansible Collections Contributor Guide
  • ansible-core Contributors Guide
  • Advanced Contributor Guide
  • Ansible documentation style guide

Extending Ansible

  • Developer Guide

Common Ansible Scenarios

  • Legacy Public Cloud Guides
  • Network Technology Guides
  • Virtualization and Containerization Guides

Network Automation

  • Network Getting Started
  • Network Advanced Topics
  • Network Developer Guide

Ansible Galaxy

  • Galaxy User Guide
  • Galaxy Developer Guide

Reference & Appendices

  • Collection Index
  • Indexes of all modules and plugins
  • Playbook Keywords
  • Return Values
  • Ansible Configuration Settings
  • Controlling how Ansible behaves: precedence rules
  • YAML Syntax
  • Python 3 Support
  • Interpreter Discovery
  • Releases and maintenance
  • Testing Strategies
  • Sanity Tests
    • action-plugin-docs
    • ansible-doc
    • ansible-requirements
    • ansible-test-future-boilerplate
    • bin-symlinks
    • botmeta
    • changelog
    • compile
    • configure-remoting-ps1
    • docs-build
    • empty-init
    • future-import-boilerplate
    • ignores
    • import
    • integration-aliases
    • line-endings
    • metaclass-boilerplate
    • mypy
    • no-assert
    • no-basestring
    • no-dict-iteritems
    • no-dict-iterkeys
    • no-dict-itervalues
    • no-get-exception
    • no-illegal-filenames
    • no-main-display
    • no-smart-quotes
    • no-unicode_literals
    • no-unwanted-files
    • obsolete-files
    • package-data
    • pep8
    • pslint
    • pylint
    • Release names
    • replace-urlopen
    • required-and-default-attributes
    • rstcheck
    • runtime-metadata.yml
    • sanity-docs
    • shebang
    • shellcheck
    • symlinks
    • test-constraints
    • use-argspec-type-path
    • use-compat-six
    • validate-modules
    • yamllint
  • Frequently Asked Questions
  • Glossary
  • Ansible Reference: Module Utilities
  • Special Variables
  • Red Hat Ansible Automation Platform
  • Ansible Automation Hub
  • Logging Ansible output

Roadmaps

  • Ansible Roadmap
  • ansible-core Roadmaps




Ansible
  • Sanity Tests
  • bin-symlinks
  • Edit on GitHub

bin-symlinks

The bin/ directory in Ansible must contain only symbolic links to executable files. These files must reside in the lib/ansible/ or test/lib/ansible_test/ directories.

This is required to allow ansible-test to work with containers and remote hosts when running from an installed version of Ansible.

Symlinks for each entry point in bin/ must also be present in test/lib/ansible_test/_util/target/injector/. Each symlink should point to the python.py script in the same directory. This facilitates running with the correct Python interpreter and enabling code coverage.

Previous Next

© Copyright Ansible project contributors. Last updated on Mar 17, 2023.