Wojciech Gębiś

I'm facing with exactly the same issue, every time `provider_config` reports changes. So for now I have to mark that field as ignored... 😞

I have experienced the same issue: ``` {"level":"warn","ts":1618589387.847299,"caller":"client/client.go:86","msg":"error fetching manifest","repo":"devops/docker-images/ansible-runner","tag":"2.9.14","error":"unexpected manifest schema was received from registry: application/vnd.docker.distribution.manifest.v2+json (registry may not support the manifest type(s) you want: [application/vnd.docker.distribution.manifest.v1+prettyjws application/vnd.docker.distribution.manifest.v1+json])"} ```

Hello, after downloaded newest config files, I see that logs: ``` 2021-09-05 16:00:41.944 [bus debug] start request 31 2021-09-05 16:00:41.944 [bus debug] arbitration start with 31 2021-09-05 16:00:42.040 [bus debug]...

and also: ``` 2021-09-05 16:02:15.503 [main error] scan config 15: ERR: arbitration lost ```

btw: when I switched to version 3.4 I got just after startup: ``` 2021-09-05 16:41:32.687 [main debug]

I'm facing the same issue. Same versions, both auth via username/password and token.

I have enabled basic auth: ``` #################################### Basic Auth ########################## [auth.basic] enabled = true ``` Both method fail :(. It worked in previous version of provider, when the Grafana objects...

Prior 1.8.0 `terraform plan` and `terraform apply` work as expected without any 403 issues.

I noticed, that it's related to `org_id` param. Then the param is passed in provider config, then permissions errors disappear.

It looks that TempDesiredHigh is corellated to the Setpoint.Monday: `$ sudo ebusctl write -c v61 TempDesiredHigh 23.5 done` `$ sudo ebusctl read -f -c v61 Setpoints.Monday 0.5;23.5;23.0`