netbox.netbox.netbox_contact_assignment module – Creates or removes contact assignments from NetBox

Note

This module is part of the netbox.netbox collection (version 3.23.0).

You might already have this collection installed if you are using the ansible package. It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.

To install it, use: ansible-galaxy collection install netbox.netbox. You need further requirements to be able to use this module, see Requirements for details.

To use it in a playbook, specify: netbox.netbox.netbox_contact_assignment.

New in netbox.netbox 3.1.0

Synopsis

  • Creates or removes contact assignments from NetBox

Requirements

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

  • pynetbox

Parameters

Parameter

Comments

cert

any

Certificate path

data

dictionary / required

Defines the contact configuration

contact

string / required

The name of the contact to assign to the object

object_name

string / required

The name of the object the contact is assigned to

object_type

string / required

The type of the object the contact is assigned to

Choices:

  • "circuit"

  • "cluster"

  • "cluster_group"

  • "device"

  • "location"

  • "manufacturer"

  • "power_panel"

  • "provider"

  • "rack"

  • "region"

  • "site"

  • "site_group"

  • "tenant"

  • "virtual_machine"

priority

string

The priority of this contact

Choices:

  • "primary"

  • "secondary"

  • "tertiary"

  • "inactive"

role

string / required

The name of the role the contact has for this object

tags

list / elements=any

Any tags that the contact may need to be associated with

headers

dictionary

Dictionary of headers to be passed to the NetBox API.

netbox_token

string / required

The NetBox API token.

netbox_url

string / required

The URL of the NetBox instance.

Must be accessible by the Ansible control host.

query_params

list / elements=string

This can be used to override the specified values in ALLOWED_QUERY_PARAMS that are defined

in plugins/module_utils/netbox_utils.py and provides control to users on what may make

an object unique in their environment.

state

string

The state of the object.

Choices:

  • "present" ← (default)

  • "absent"

validate_certs

any

If no, SSL certificates will not be validated.

This should only be used on personally controlled sites using a self-signed certificates.

Default: true

Notes

Note

  • Tags should be defined as a YAML list

  • This should be ran with connection local and hosts localhost

Examples

- name: "Test NetBox module"
  connection: local
  hosts: localhost
  gather_facts: false
  tasks:
    - name: Assign a contact to a location with only required information
      netbox.netbox.netbox_contact_assignment:
        netbox_url: http://netbox.local
        netbox_token: thisIsMyToken
        data:
          object_type: location
          object_name: My Location
          contact: John Doe
          role: Supervisor Role
        state: present

    - name: Delete contact assignment within netbox
      netbox.netbox.netbox_contact_assignment:
        netbox_url: http://netbox.local
        netbox_token: thisIsMyToken
        data:
          object_type: location
          object_name: My Location
          contact: John Doe
          role: Supervisor Role
        state: absent

    - name: Create contact with all parameters
      netbox.netbox.netbox_contact:
        netbox_url: http://netbox.local
        netbox_token: thisIsMyToken
        data:
          object_type: location
          object_name: My Location
          contact: John Doe
          role: Supervisor Role
          priority: tertiary
          tags:
            - tagA
            - tagB
            - tagC
        state: present

Return Values

Common return values are documented here, the following are the fields unique to this module:

Key

Description

contact_assignment

dictionary

Serialized object as created or already existent within NetBox

Returned: on creation

msg

string

Message indicating failure or info about what has been achieved

Returned: always

Authors

  • Daniel Chiquito (@dchiquito)