Jens Hausherr

Here is another one. Apparently the provider cannot reconcile Helm's semver spec (`^1.3 ^= ~>1.3`) with the resolved effective version: ``` ╷ │ Error: Provider produced inconsistent final plan │...

Hi @TomChv, please fork the repo, push your changes there and open a PR so we can discuss the changes

The operator uses [kubernetes/klog](https://github.com/kubernetes/klog) for its logging. The log event format is described here: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md#logging-formats

I think the main issue is that it uses the vanilla (internal?) codegen, which also lacks flexibility to be used as external tooling (e.g. always generating a `@pulumi/` scope for...

I really should move this to Github actions, but this repo is admittedly low on my priority list

I also tried with VNC viewer. It also reports occasionally errors in the XRLE encoding, but it is much more robust and does not drop the connection. I'll see if...

Looks like I missed a spot. I also had this in my cluster. I'll take another look.

IMO there is little database logic involved. When the deletionTimestamp is set on the Grant resource the reconciliation should not fail and prevent removing the finalizer if it is already...

The PR is not good-to-go yet, I would first like to verify the approach taken (and I need to find some time to spend on testing it 😬 )

Ran into the issue as well while generating code for nodejs/typescript from the grafana-operator: Sample output: Invalid type names generated ```typescript export interface GrafanaSpecConfigExternal_image_storage.azure_blob { account_key?: string; account_name?: string; container_name?:...