What problem are you facing?
Many Crossplane users rely on configuration packages from a crossplane.yaml rather than Projects.
The dependency tooling in the CLI relies on project files instead.
For example, the crossplane dependency update-cache, clean-cache and add subcommands only accept a project file (-f, which defaults to crossplane-project.yaml). They fail on a crossplane.yaml pkg meta file.
crossplane render xr already autodetects a project file or a crossplane.yaml, but render op and the dependency subcommands do not.
How could Crossplane help solve your problem?
Treat the package metadata file as a first-class input wherever the CLI only needs a package's dependencies.
What problem are you facing?
Many Crossplane users rely on configuration packages from a
crossplane.yamlrather than Projects.The dependency tooling in the CLI relies on project files instead.
For example, the
crossplane dependency update-cache,clean-cacheandaddsubcommands only accept a project file (-f, which defaults tocrossplane-project.yaml). They fail on acrossplane.yamlpkg meta file.crossplane render xralready autodetects a project file or acrossplane.yaml, butrender opand thedependencysubcommands do not.How could Crossplane help solve your problem?
Treat the package metadata file as a first-class input wherever the CLI only needs a package's dependencies.