-
Notifications
You must be signed in to change notification settings - Fork 910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Introduction of skipDependencyResolution
Field for dependsOn in Configurations
#5279
Comments
skipDependencyResolution
Field for dependsOn in Configurations
skipDependencyResolution
Field for dependsOn in Configurations
Can you give some examples of a dependency being unnecessary or problematic? If a dependency was unnecessary, wouldn't you just not list it as a dependency of the configuration? dependsOn:
- configuration: xpkg.upbound.io/upbound/configuration-aws-eks-karpenter
version: "v0.5.0"
skipDependencyResolution: true Does this then become information purely for human consumption? Should I read it as:
If so, I would suggest |
I had the same reaction when I read the description, but I think the It seems a little odd to specify this inside the definition of the Configuration itself - it seems like something that the package deployer would want to control more than the package author. What happens if this Configuration is installed in a Crossplane cluster that doesn't have the skipped "sub-dependencies" installed? |
Add a PR for this #5285 add description and some live tests - feel free to discuss |
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as |
/fresh |
What problem are you facing?
This proposal suggests introducing a
skipDependencyResolution
field for thedependsOn
attribute within configurations. In current practice, dependency resolution can be skipped only at a global configuration level. However, this often does not suffice for the nuanced needs of complex platform projects, especially in large companies where fulfilling all dependencies in a configuration can be challenging (Security, External Registries, same APIs Inhouse with additional features). The proposed feature aims to provide more granular control over dependency resolution within individual configurations.Many companies, especially those with large platform projects, frequently encounter difficulties in managing dependencies within their configurations. The current approach allows for skipping dependency resolution for the entire configuration, which is often a blunt tool for what requires a more precise solution. https://doc.crds.dev/github.com/crossplane/crossplane/pkg.crossplane.io/Configuration/[email protected]#spec-skipDependencyResolution
How could Crossplane help solve your problem?
The proposed solution is to introduce a new field,
skipDependencyResolution
, that can be used within thedependsOn
attribute in configuration. This field would allow platform builders to specify if dependency resolution should be skipped for particular dependencies, rather than applying this skip to the entire configuration.The primary benefit of this feature is the increased control it offers platform builders over their configurations. By allowing dependency resolution to be skipped on a per-dependency basis, teams can manage their configurations more effectively, especially in scenarios where certain dependencies are known to be unnecessary or problematic. This flexibility is particularly valuable in large-scale platform projects where managing a vast number of dependencies can be challenging.
Implementation Considerations
The text was updated successfully, but these errors were encountered: