-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nios_network add field to specify a template to use for network creation #61
Comments
From @ansibullbot on May 27, 2020 23:54 Files identified in the description:
If these files are inaccurate, please update the |
From @ansibullbot on May 27, 2020 23:54 cc @NilashishC @Qalthos @danielmellado @ebirn @ganeshrn @justjais @krisvasudevan @nerzhul @privateip @sganesh-infoblox @sjaiswal @trishnaguha |
From @russoz on May 19, 2021 21:43 Hi there The main development of the nios modules has moved over to https://github.com/infobloxopen/infoblox-ansible/ You should probably create the same issue there and close this one. The nios modules are set for deprecation in community.general on version 5.0.0 (spring 2022, still far away but nonetheless set). Thanks for your contribution! |
From @noziwatele on May 27, 2020 23:53
SUMMARY
When a network is created in NIOS a pre-defined template can be specified that automatically creates commonly used objects within the new network, such as fixed addresses/reservations for router IPs, DHCP ranges, etc.
It would be great if a template could be specified by name in a field in the nios_network module. Other nios_ modules could possibly also use templates.
ISSUE TYPE
COMPONENT NAME
nios_network
(could also be added to other nios_* modules for objects that support templates)
ADDITIONAL INFORMATION
A string field would be added, possibly named 'template', that would be used to specify the template to be used. This is passed directly through to the NIOS API or infoblox_client module in the template=TEMPLATE_NAME argument.
Copied from original issue: ansible/ansible#424
The text was updated successfully, but these errors were encountered: