Mik Szillat

The generic secret resource doesn't work for me. The data written is only the configuration of the issued token and doesn't get stored in the backend. Maybe this is an...

The thing is that I use the data for configuring another provider and this doesn't work with regular resources, as they are only evaluated after initializing the providers.

I'm using a plugin to fetch a token for configuring the GitHub provider. The plugin can be configured to issue tokens with specific scopes by adding data to the request....

It seems that the "Accept: application/json" header is missing in the request update: we investigated the issue and discovered that the request sets the 'content-type' header, which is technically not...

I think the "Content-type" header really has to be removed; "Accept" is technically correct and sufficient. The parser error indicates that Ansible tries to parse the returned data as YAML,...

I tested the public NetBox with the same parameters as above and with some additional tests. The public NetBox behaves as it should. Note that when requesting with the 'Accept'...

This happened to us after importing the resource into the Terraform state. When creating the resource as new, the attribute 'api_key' appeared in the output.

Also still occurring on 3.17.0

I have just tried this and it doesn't work. After manually editing the deployment resource, some automation supersedes the operation and puts the old version back in place: > Operation...

I just looked again into the issue and found that you can perform an upgrade with the following Azure CLI command: ``` az aks addon update \ --addon ingress-appgw \...