New in version 2.3.
- aos-pyez >= 0.6.0
parameter | required | default | choices | comments |
---|---|---|---|---|
content |
no | Datastructure of the ASN Pool to manage. The data can be in YAML / JSON or directly a variable. It's the same datastructure that is returned on success in value. | ||
id |
no | AOS Id of the ASN Pool to manage. Only one of name, id or content can be set. | ||
name |
no | Name of the ASN Pool to manage. Only one of name, id or content can be set. | ||
ranges |
no | List of ASNs ranges to add to the ASN Pool. Each range must have 2 values. | ||
session |
yes | An existing AOS session as obtained by aos_login module. | ||
state |
no | present |
|
Indicate what is the expected state of the ASN Pool (present or not). |
- name: "Create ASN Pool" aos_asn_pool: session: "{{ aos_session }}" name: "my-asn-pool" ranges: - [ 100, 200 ] state: present register: asnpool - name: "Save ASN Pool into a file in JSON" copy: content: "{{ asnpool.value | to_nice_json }}" dest: resources/asn_pool_saved.json - name: "Save ASN Pool into a file in YAML" copy: content: "{{ asnpool.value | to_nice_yaml }}" dest: resources/asn_pool_saved.yaml - name: "Delete ASN Pool" aos_asn_pool: session: "{{ aos_session }}" name: "my-asn-pool" state: absent - name: "Load ASN Pool from File(JSON)" aos_asn_pool: session: "{{ aos_session }}" content: "{{ lookup('file', 'resources/asn_pool_saved.json') }}" state: present - name: "Delete ASN Pool from File(JSON)" aos_asn_pool: session: "{{ aos_session }}" content: "{{ lookup('file', 'resources/asn_pool_saved.json') }}" state: absent - name: "Load ASN Pool from File(Yaml)" aos_asn_pool: session: "{{ aos_session }}" content: "{{ lookup('file', 'resources/asn_pool_saved.yaml') }}" state: present register: test - name: "Delete ASN Pool from File(Yaml)" aos_asn_pool: session: "{{ aos_session }}" content: "{{ lookup('file', 'resources/asn_pool_saved.yaml') }}" state: absent
This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.
This module is community maintained without core committer oversight.
For more information on what this means please read Module Support
For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Helping Testing PRs and Developing Modules.