Releases: Cloud-Temple/yaani
Releases · Cloud-Temple/yaani
v2.0.0 [2020-05-07]
Enhancements
- Multi-source declaration
- Multiple source types support
- Specific data set extraction & recombination
- Multiple rendering section
- Rendering inclusion conditions
- Group parenting implementation
- Group vars implementation
Breaking changes
The configuration file structure and instructions have changed. Please make sure to update yours before.
v1.1 [2019-12-5]
Add API section configuration through environment variables feature.
Major Upgrade and test addition
Merge pull request #40 from a-delannoy/master Major Upgrade and test addition
Fix exception raising when called with --host <unknown host>
v0.2.1 Fix: exception when called with --host <unknown host>
v0.2.0
Breaking changes in configuration file:
- API keywords are no more prefixed with the 'api_' particle and are now passed to pynetbox.
- The former 'filter' field is now used with an 's' as 'filters' and is now a dictionnary of arguments that are passed to pynetbox.
- The import statement are now located one step deeper in enclosing sections. Each one of these envelop is named after a netbox django application. For example, devices are now in the 'dcim' envelop.
The requests is no longer directly used to interact with netbox api. Instead, pynetbox has been introduced.
More object types are now supported in 'import'.
Initial Yaani release
Yanni first release allows you to
- Generate a dynamic inventory for Ansible from Netbox (like any other Netbox dynamic inventory)
- Fetch different element from Netbox such as devices, racks and others.
- Filter the element you want to pull
- Load any variables form netbox
- Group by any keys (tags, roles, etc.)