Feature: Client Resources

[offbyone]

• added getters for the list of client / autoclient / supported tags resources

---

Proposed Changes

Adding support for the Client / AutoClient resources in AdGuard Home

The first commit here is to open discussion on structure and naming; if this is desirable in this state, I will add the update operations to it as well.

I don't intend to get super clever with remote ORM stuff here; I only want to have simple "add", "update", "delete" methods for them that refer to the APIs directly.

Related Issues

(Github link to related issues or pull requests)

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

No Coverage information
0.0% Duplication

[bendalton]

I'll ping too. Please test/merge this. I'd like to use it upstream with HomeAssistant

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

No Coverage information
0.0% Duplication

[frenck]

I'll ping too. Please test/merge this. I'd like to use it upstream with HomeAssistant

I hate to bring it to you, but if you goal is to use this in Home Assistant: You can't.

To make this possible, we need an identifier. A request for this is open @ the AdGuard Home team.

So, if that is your only goal, I suggest closing this PR as it has no foreseeing future.

[offbyone]

Nope, I'm using this for scripting independent of HA.

[frenck]

Sorry I now realize I responded to a non-author, sorry about that 👍

../Frenck

[offbyone]

Okay; I'll add update methods here as well and then update the PR. Thanks.

[offbyone]

I'm still interested in merging this, just haven't had the time to finish it up.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

No Coverage information
0.0% Duplication

[offbyone]

I am still interested in merging this, I just need the maintainer to okay it.

[offbyone]

I would still like to see this merge.

[offbyone]

@frenck if you are not interested in maintaining this -- and that's entirely fair! -- how about discussing handing it off? I'm interested and willing.

[frenck]

@frenck if you are not interested in maintaining this

I am, sorry. I don't see the use case for Home Assistant in this regard (which is the primary use of this library).

how about discussing handing it off?

Because I haven't merged your itch? 🤷 Sorry, nope.

[offbyone]

So, for clarity, this isn't a "Python" adguard client, it is a home assistant adguard client library that happens to be written in Python?

[frenck]

From the readme:

There is my main use case. Right now, I'm drinking a few beers, so not going to dive in. I can try to make some time tomorrow morning.

../Frenck

[offbyone]

Mostly I'd like to know if this is considered a general purpose client library for the Adguard API, with features that are usable outside of HA, or if additions will purely be considered in the context of whether they are usable for HA. I've got some decisions to make about how I use it depending on that. The README indicates that home assistant is an example of an integration, not the only one that matters. Can you clarify please?