Skip to content

Cut off phpipam api calls from phpipam_utils.py to make it more plugins available. #72

@cmeissner

Description

@cmeissner
Member

Is your feature request related to a problem? Please describe.
In the early beginning of this project we decided to put all api calls inside classes where all modules derive from.
This was fine until we want to start developing plugins such as lookup and inventory plugins. This plugin classes can not be derived from PhpipamAnsibleModule or PhpipamEntityAnsibleModule.

Describe the solution you'd like
Now it is time to create a module which provides a phpipam related classes and methods in a way we can use it for all kinds of plugins.
After creating such a module we can use it for all our plugins and modules. Another benifit will be that we can hide handling of strange different api calls from the user but we provide a common way. See it like a layer of abstraction.

Activity

self-assigned this
on Jan 6, 2022
linked a pull request that will close this issueRefactoring_api_interactions #71on Jan 6, 2022
added this to the v2 milestone on Jan 6, 2022
github-actions

github-actions commented on Sep 5, 2023

@github-actions

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

Relationships

None yet

    Development

    Participants

    @cmeissner

    Issue actions

      Cut off phpipam api calls from `phpipam_utils.py` to make it more plugins available. · Issue #72 · codeaffen/phpipam-ansible-modules