Skip to content

docs: clarify the package-health check in the test-examples skill - #78

Merged
jbw976 merged 1 commit into
crossplane-contrib:mainfrom
jbw976:clarify-test-examples-pkg-check
Jun 14, 2026
Merged

docs: clarify the package-health check in the test-examples skill#78
jbw976 merged 1 commit into
crossplane-contrib:mainfrom
jbw976:clarify-test-examples-pkg-check

Conversation

@jbw976

@jbw976 jbw976 commented Jun 14, 2026

Copy link
Copy Markdown
Member

Description of your changes

The Phase 1 setup check in the test-examples skill told the runner to verify packages with a one-shot kubectl get pkg showing INSTALLED=True / HEALTHY=True, but never said packages take a few minutes to pull or how to wait for them.

That gap invited ad-hoc awk-based poll loops that never converge: kubectl get pkg prints separate Function and Provider tables, each with its own header row, so column counting against a single header never matches.

This clarifies that the check needs polling, and routes to the same grep True/False approach the skill already documents for trace parsing in Phase 3.2. Docs-only change to the skill under .claude/; no behavior change to the examples.

I have:

  • Read and followed Crossplane's contribution process.
  • Added or updated unit tests for my change. Docs-only change to a skill file; no unit tests apply.

The Phase 1 setup check didn't say packages take a few minutes to pull or
how to wait for them, which invited ad-hoc awk-based poll loops that never
converge because `kubectl get pkg` prints separate Function and Provider
tables with their own header rows. Spell out that the check needs polling,
and reuse the `grep True/False` pattern already documented in Phase 3.2.

Signed-off-by: Jared Watts <jbw976@gmail.com>
@jbw976
jbw976 merged commit a0b4c08 into crossplane-contrib:main Jun 14, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant