Skip to content

Ansible Support #27

@mrmrcoleman

Description

@mrmrcoleman

Plugin Version

commit 722bbd6 (HEAD -> public-preview, origin/public-preview) Author: btiemann [email protected] Date: Thu Jun 26 15:31:01 2025 -0400

Proposed functionality

Many users use Ansible and allowing users to create their own custom object types and custom objects means that we also need a way to make the Ansible provider aware of these new objects

Context/Background

This is a broader issue that requires that we are able to generate changes to external tooling like pynetbox, Ansible and also Diode. There is a separate issue for pynetbox support for Custom Objects which is a prerequisite for Ansible support.

Impact

Users will be able to interact with their new objects using their existing automation tooling

Use case

As a user I am able to run the usual CRUD operations on Custom Object Types, Custom Object Fields and Custom Objects, using Ansible.

Further specific use cases to follow.

External dependencies

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions