Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: API-usage refactoring #51

Open
ansibleguy opened this issue Jan 10, 2024 · 3 comments
Open

Feature: API-usage refactoring #51

ansibleguy opened this issue Jan 10, 2024 · 3 comments
Assignees
Labels
api-fix API Fixes enhancement New feature or request prio-high High Priority

Comments

@ansibleguy
Copy link
Owner

Link to API

Description

The /get API endpoints will change in a major way in the future - as described in this OPNSense issue.
We will have to refactor our existing API implementation:
OPNSense API usage

This should be implemented as abstracted/shared logic: https://opnsense.ansibleguy.net/en/latest/usage/4_develop.html#abstraction

@ansibleguy ansibleguy added enhancement New feature or request triage labels Jan 10, 2024
@ansibleguy ansibleguy self-assigned this Jan 10, 2024
@ansibleguy ansibleguy added enhancement New feature or request api-fix API Fixes and removed enhancement New feature or request triage labels Jan 10, 2024
@enmanuelmoreira

This comment was marked as off-topic.

@ansibleguy

This comment was marked as off-topic.

@enmanuelmoreira

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-fix API Fixes enhancement New feature or request prio-high High Priority
Projects
None yet
Development

No branches or pull requests

2 participants