aci_contract_subject_to_filter - Bind Contract Subjects to Filters on Cisco ACI fabrics (vz:RsSubjFiltAtt)

New in version 2.4.

Synopsis

Requirements (on host that executes module)

  • ACI Fabric 1.0(3f)+

Options

parameter required default choices comments
contract
 no
The name of the contract.
aliases: contract_name
filter
 no
The name of the Filter to bind to the Subject.
hostname
 yes
IP Address or hostname of APIC resolvable by Ansible control host.
aliases: host
log
 no none
  • log
  • none
Determines if the binding should be set to log.
The APIC defaults new Subject to Filter bindings to none.
aliases: directive
password
 yes
The password to use for authentication.
state
 no present
  • absent
  • present
  • query
Use present or absent for adding or removing.
Use query for listing an object or multiple objects.
subject
 no
The name of the Contract Subject.
aliases: contract_subject, subject_name
tenant
 yes
The name of the tenant.
aliases: tenant_name
timeout
 no 30
The socket level timeout in seconds.
use_proxy
 no yes
  • yes
  • no
If no, it will not use a proxy, even if one is defined in an environment variable on the target hosts.
use_ssl
 no yes
  • yes
  • no
If no, an HTTP connection will be used instead of the default HTTPS connection.
username
 yes admin
The username to use for authentication.
aliases: user
validate_certs
 no yes
  • yes
  • no
If no, SSL certificates will not be validated.
This should only set to no used on personally controlled sites using self-signed certificates.

Examples

- aci_subject_filter_binding:
    hostname: '{{ inventory_hostname }}'
    username: '{{ username }}'
    password: '{{ password }}'
    tenant: '{{ tenant }}'
    contract: '{{ contract }}'
    subject: '{{ subject }}'
    filter: '{{ filter }}'
    log: '{{ log }}'

Notes

Note

  • The tenant, contract, subject, and filter_name must exist before using this module in your playbook.
  • The aci_tenant, aci_contract, aci_contract_subject, and aci_filter modules can be used for these.
  • By default, if an environment variable <protocol>_proxy is set on the target host, requests will be sent through that proxy. This behaviour can be overridden by setting a variable for this task (see setting the environment), or by using the use_proxy option.
  • HTTP redirects can redirect from HTTP to HTTPS so you should be sure that your proxy environment for both protocols is correct.

Status

This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.

For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Testing Ansible and Developing Modules.

© 2012–2018 Michael DeHaan
© 2018–2019 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.4/aci_contract_subject_to_filter_module.html