If you use the persistent cache, inventory plugins can also use the configured cache plugin to store and retrieve data. However, you can use the meta: refresh_inventory task to clear the current inventory and execute the inventory plugins again, and this task will generate a new inventory. Normally, inventory plugins are executed at the start of a run, and before the playbooks, plays, or roles are loaded.
You should read that document first for a general understanding and then come back to this document for specifics on inventory plugins. Most of the documentation in Developing plugins also applies here. They execute on the controller and should therefore adhere to the Control node requirements. Like most plugin types (except modules), inventory plugins must be developed in Python. The table below shows some examples of inventory plugins and the source types that you can pass to them with -i on the command line. Inventory sources are the input strings that inventory plugins work with.Īn inventory source can be a path to a file or to a script, or it can be raw data that the plugin can interpret. If you use inventory plugins instead, you can use the Ansible codebase and add these common features automatically. If you choose to write a script, however, you will need to implement some features yourself such as caching, configuration management, dynamic variable and group composition, and so on. You can still use and write inventory scripts, as we ensured backwards compatibility via the script inventory pluginĪnd there is no restriction on the programming language used. In previous versions, you had to create a script or program that could output JSON in the correct format when invoked with the proper arguments. If the source you want is not currently covered by existing plugins, you can create your own inventory plugin as with any other plugin type.
#Amazon flat file inventory loader how to
For details about how to pull inventory information, see Working with dynamic inventory.
Guidelines for Ansible Amazon AWS module development.Contributing your module to an existing Ansible collection.
0 kommentar(er)
