Documentation

aci_epg_to_contract - Bind EPGs to Contracts on Cisco ACI fabrics (fv:RsCons and fv:RsProv)

New in version 2.4.

Synopsis

Options

parameter required default choices comments
ap
 no
Name of an existing application network profile, that will contain the EPGs.

aliases: app_profile, app_profile_name
contract
 no
The name of the contract.

aliases: contract_name
contract_type
 yes
  • consumer
  • proivder
Determines if the EPG should Provide or Consume the Contract.
epg
 no
The name of the end point group.

aliases: epg_name
hostname
 yes
IP Address or hostname of APIC resolvable by Ansible control host.

aliases: host
password
 yes
The password to use for authentication.
priority
 no unspecified
  • level1
  • level2
  • level3
  • unspecified
QoS class.
The APIC defaults new EPG to Contract bindings to unspecified.
provider_match
 no at_least_one
  • all
  • at_least_one
  • at_most_one
  • none
The matching algorithm for Provided Contracts.
The APIC defaults new EPG to Provided Contracts to at_least_one.
state
 no present
  • absent
  • present
  • query
Use present or absent for adding or removing.
Use query for listing an object or multiple objects.
tenant
 no
Name of an existing 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.

Notes

Note

  • The tenant, app_profile, EPG, and Contract used must exist before using this module in your playbook. The aci_tenant, aci_ap, aci_epg, and aci_contract modules can be used for this.
  • 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.