-
Notifications
You must be signed in to change notification settings - Fork 49
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
fortios_export_config_playbook - system_settings selector not working #322
Comments
Hi @dominicfillmore , Thank you for raising this issue, I can reproduce that, and have reported it to the dev team for fixing. Thanks, |
Hi @dominicfillmore , We just released Ansible FOS 2.3.7. This issue should be fixed, so you could upgrade to it and give it a try at your convenience.
Thanks, |
Thanks Maxx, This runs now. Whatever VDOM I specify in the playbook I run, the resulting playbook that this on generates will always have the values for the VDOM I specified, but have "vdom: root" in the vars. I've noticed this with quite a few of the other selectors. Is this on purpose or a bug? Ideally I should be able to run the playbook this generates without modification to restore whatever selectors I specify when I run it |
Hi @dominicfillmore , We have improved this aspect. Since the exported playbook is a hardcoded template except for the tasks section, it may cause confusion. In the latest Ansible FOS collections, we have highlighted the customized parts that customers need to specify. Let me know if you still have quesitons.
|
I have a playbook that can access loads of other selectors fine, but if I try system_settings selector, I get an error - "The error was: AttributeError: 'list' object has no attribute 'split'"
The text was updated successfully, but these errors were encountered: