Crossplane function - Cannot resolve package dependencies: cannot initialize dependency graph from the packages in the lock about crossplane HOT 4 OPEN

The error about patch and transform is self explanatory and as of now i don't want two version of function,but maybe be useful in future provided we fix crd for input i don't have a use case as of now on that.

My only concern is that individual functions should be independent of each other since they don't share anything between them,function sequencer should be in healthy state irrespective of whatever happening for patch and transform.

Function should be independent of each other they use diff input crds,runs on diff pods why should it be dependent on another I don't believe that should the way it should work.

from crossplane.

Thanks for opening this issue and providing more context @btwseeu78!

I'd love to understand your scenario a bit better - is there a reason you're hoping to have more than 1 version of function-patch-and-transform installed in the control plane? what does your ideal outcome look like if your scenario worked as intended? 🤔

I think in general it's not supported to install 2 copies of the same function right now - I can essentially reproduce this same scenario just installing function-patch-and-transform twice, without function-sequencer. I think for function-sequencer, you're getting the error message about function-patch-and-transform in the lock file, which is a bit misleading, because the lock file as a whole is in an unsupported state due to the duplicated functions, and therefore the package manager can't even try to think about function-sequencer's dependencies (of which there are actually none). I think this is what's happening here 😇

Here's a repro of this scenario with just 2 function-patch-and-transform:

apiVersion: pkg.crossplane.io/v1beta1
kind: Function
metadata:
  name: function-patch-and-transform
spec:
  package: xpkg.upbound.io/crossplane-contrib/function-patch-and-transform:v0.4.0

apiVersion: pkg.crossplane.io/v1beta1
kind: Function
metadata:
  name: function-patch-and-transform-2
spec:
  package: xpkg.upbound.io/crossplane-contrib/function-patch-and-transform:v0.4.0

from crossplane.

Yes, we could probably avoid getting the lock in a knowingly inconsistent state beforehand 🤔

from crossplane.

Related old issue: #3423

from crossplane.