`crossplane dependency update-cache` does not add XRD types into `schemas/` (inconsistent with `crossplane project build`)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Reproduce the issue with crossplane project init, an XRD under apis/, and crossplane dependency update-cache; inspect schemas/.lock.json and the generated schemas. Compare the result with crossplane project build, which adds the fs://apis entry. Done means update-cache includes the XRD schemas and updates the lock file without requiring a full build.
Written by the indexing model from the issue text.
Description
What happened?
After running crossplane dependency update-cache, schemas/.lock.json does not include entries for XRD schemas defined under apis/. Only running crossplane project build updates the lock file and adds a fs://apis key with the generated schemas.
This makes the two commands inconsistent: one partially updates the cache/lock file, the other fully updates it. In practice this breaks the local dev loop — since update-cache doesn't pick up XRD changes, a full project build is required after every schema edit just to regenerate the schemas needed to keep developing a function.
I expected update-cache to update the lock file and the schema types consistently, including XRD schema entries, without requiring a full build.
How can we reproduce it?
crossplane project init my-project- Add dependencies to
crossplane-project.yaml - Add an XRD definition to
apis/ crossplane dependency update-cache- Inspect
schemas/— the lock file does not contain thefs://apiskey, and no schemas were generated for it crossplane project build- Inspect
schemas/again — the lock file now containsfs://apis, and the schemas have been generated
What environment did it happen in?
- Crossplane CLI version: 2.4.0
- Platform: linux/amd64
- Dominant language
- Go
- Stars
- 19
- Forks
- 31
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 53
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from crossplane/cli
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
crossplane/cli#282 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
crossplane/cli#384 ·
-
crossplane/cli#379 · 1 assignee ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 68/100
crossplane/cli#370 · 1 reaction ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 28/100
crossplane/cli#369 ·
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Bob Shell support Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
santhosh-tekuri/jsonschema#276 ·