Stefan Prodan

Are you using `dependsOn` in HelmReleases or in Flux Kustomizations?

@llanos1205 using a user password is not what we have in the [Azure DevOps docs](https://fluxcd.io/flux/use-cases/azure/): > If you wish to use Git over HTTPS, then generate a personal access token...

Can you please bump the source objects in your repo to v1beta2 and upgrade to latest Flux.

> then chart update in GitRepository triggers HelmRelease reconciliation Yes all Flux reconcilers are triggered by source changes that's by design.

> If so, interval on a HelmRelease does not make much sense, since it's driven by its source anyway. The interval is there because Kubernetes events are not guaranteed, due...

This is also the case for HelmReleases

@carlosonunez-vmw please squash the two commits

I'm not for adding the ref to metrics, a ref in spec can be a semver rage or a commit SHA, if we report the resolved ref then our metrics...

Remote bases bypass source-controller so they break many of Flux promises: as we don’t verify nor do we store the remote sources in-cluster as Flux artifacts. Pulling remote bases at...

I'm assigning RFC-0004 for this one, @aryan9600 please add `Last update` to today, and mark the PR ready.