Karl Schriek

Yes, in fact at the moment we roll out MLFlow within our Kubeflow Cluster, as it seems to be the most mature solution that is currently out there. However, MLFlow...

Maybe just to clarify a bit, it actually does make sense that `$(System.AccessToken)` would not be able to do this, since it doesn't have any rights on AAD/ARM, which presumably...

The workaround appears to be to set `namespace = ""`

I am removing the "WIP" label since it it seems that otherwise no one will look at this. It is not ready to be merged yet though.

I see! I'll add that same check then. Yes, both managed identities and workload identities are "ambient", at least as far as I understand how you define it. A managed...

Ok I have now incorporated the discussion points above. Have also significantly simplified the PR. Previously I was introducing a new flag "useWorkloadIdentity" which needed to be explicitly toggled to...

I have started looking at how this could be implemented. It looks like it should be quite straightforward, namely: 1. In go.mod, set `github.com/hashicorp/go-azure-helpers v0.40.0` 2. In internal/backend/remote-state/azure/arm_client.go, add the...

Note, the above is based on branching from tag v1.2.9. I am happy to have a go at submitting a PR, but since the first RC for 1.3.0 has just...

Sure I'm happy to have a go at a PR. Anything I should know? Otherwise I'll just branch from HEAD and add the changes as described above.

I see a note all the way back in https://github.com/kubernetes-sigs/kustomize/releases/tag/api%2Fv0.8.11 that forced line wrapping is supposed to no longer be present. Doesn't seem to be the case though, at least...