Joshua Spence

Sorry, life got in the way

Sorry for the delay, life got in the way. I'll try to catch up on the PR backlog over the next week or two.

We only support stable releases, I think 7.4 is still in EA?

I think we could add a `wait_for_ip` parameter to the data source for this purpose. Alternatively, we could implement a `unifi_user_ip` data source.

Can you post debug logs?

So what's happening here is that the provider updates the network by hitting `/proxy/network/api/s/default/rest/networkconf/641939a7b17a3e10ccfd10c6` and Unifi Network responds with the following response: ``` {"meta":{"rc":"ok"},"data":[]} ``` This is unexpected as it...

I am not using this component anymore but it looks like it will be tricky to fix this. The incompatible code isn't in the component but is in a dependency....

+1

It doesn't seem to work, unless I am missing something. ``` $ chezmoi --version chezmoi version dev, commit 95f58622290fda3494bf829c7cb5c3a6ea2b7c29, built at 2024-05-02T21:17:02Z $ chezmoi execute-template '{{ gitHubLatestRelease "REDACTED_HOST/REDACTED_OWNER/REDACTED_REPO" }}' chezmoi:...

It does seem to be using the correct access token though, just passing it to the wrong endpoint