fmgr_securityconsole_install_package – Copy and install a policy package to devices.

New in version 2.10.

Synopsis

  • This module is able to configure a FortiManager device by allowing the user to [exec] the following FortiManager json-rpc urls.
  • /securityconsole/install/package
  • Examples include all parameters and values need to be adjusted to data sources before usage.
  • Tested with FortiManager v6.0.0

Requirements

The below requirements are needed on the host that executes this module.

  • ansible>=2.10.0

Parameters

  • loose_validation - Do parameter validation in a loose way type: bool required: false default: false
  • workspace_locking_adom - Acquire the workspace lock if FortiManager is running in workspace mode type: str required: false choices: global, custom dom
  • workspace_locking_timeout - The maximum time in seconds to wait for other users to release workspace lock type: integer required: false default: 300
  • parameters for method: [exec] - Copy and install a policy package to devices.
    • data - No description for the parameter type: dict
      • adom - Source ADOM name. type: str
      • adom_rev_comments - If "generate_rev" flag is set, the comment for the new ADOM revision. type: str
      • adom_rev_name - If "generate_rev" flag is set, the name for the new ADOM revision. type: str
      • dev_rev_comments - Comments for the device configuration revision that will be generated during install. type: str
      • flags - No description for the parameter type: array
        • {no-name} - No description for the parameter type: str choices: [none, cp_all_objs, preview, generate_rev, copy_assigned_pkg, unassign, ifpolicy_only, no_ifpolicy, objs_only, auto_lock_ws, check_pkg_st, copy_only]
      • pkg - Source package path and name. type: str
      • scope - No description for the parameter type: array
        • name - No description for the parameter type: str
        • vdom - No description for the parameter type: str

Notes

Note

  • The module may supports multiple method, every method has different parameters definition
  • One method may also have more than one parameter definition collection, each collection is dedicated to one API endpoint
  • The module may include domain dependent urls, the domain can be specified in url_params as adom
  • To run in workspace mode, the paremeter workspace_locking_adom must be included in the task

Examples

- hosts: fortimanager-inventory
  collections:
    - fortinet.fortimanager
  connection: httpapi
  vars:
     ansible_httpapi_use_ssl: True
     ansible_httpapi_validate_certs: False
     ansible_httpapi_port: 443
  tasks:

   - name: REQUESTING /SECURITYCONSOLE/INSTALL/PACKAGE
     fmgr_securityconsole_install_package:
        loose_validation: False
        workspace_locking_adom: <value in [global, custom adom]>
        workspace_locking_timeout: 300
        method: <value in [exec]>
        params:
           -
              data:
                 adom: <value of string>
                 adom_rev_comments: <value of string>
                 adom_rev_name: <value of string>
                 dev_rev_comments: <value of string>
                 flags:
                   - <value in [none, cp_all_objs, preview, ...]>
                 pkg: <value of string>
                 scope:
                   -
                       name: <value of string>
                       vdom: <value of string>

Return Values

Common return values are documented: https://docs.ansible.com/ansible/latest/reference_appendices/common_return_values.html#common-return-values, the following are the fields unique to this module:

  • return values for method: [exec]
    • data - No description for the parameter type: dict
      • task - No description for the parameter type: str
    • status - No description for the parameter type: dict
      • code - No description for the parameter type: int
      • message - No description for the parameter type: str
    • url - No description for the parameter type: str example: /securityconsole/install/package

Status

  • This module is not guaranteed to have a backwards compatible interface.

Authors

  • Frank Shen (@fshen01)
  • Link Zheng (@zhengl)

Hint

If you notice any issues in this documentation, you can create a pull request to improve it.