Support dependecies with version constraints in crank validate #5669
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your changes
This PR continuation of the PR #5570 where I have pointed out that the
crossplane beta validate
doesn't work withConfiguratons
that contain version constraints. This PR is trying to address that.I have:
Added or updated unit tests.Added or updated e2e tests.Linked a PR or a docs tracking issue to document this change.Added backport release-x.y labels to auto-backport this PR.The PR was tested like this:
Clone the repo, apply the patch and build a new
crank
binary:Create directory structure for the test:
mkdir -p /tmp/{apis/foo.custom-api.example.org,test/{functions,validation}} cd /tmp/test
Create files:
Run local Docker registry:
Package and push the
foo
package:Validate the
Bar
composition using the upstreamcrank
binary:Validate the
Bar
composition using the patchedcrank
binary: