Skip to content

dependencies: add shared lemonade-ready readiness check - #680

Open
lucbruni-amd wants to merge 1 commit into
mainfrom
ci-shared-lemonade-ready-check
Open

dependencies: add shared lemonade-ready readiness check#680
lucbruni-amd wants to merge 1 commit into
mainfrom
ci-shared-lemonade-ready-check

Conversation

@lucbruni-amd

Copy link
Copy Markdown
Collaborator

Adds a require-able readiness gate under a new dependencies/checks/ namespace (registry category: check). @require:lemonade-ready waits for the Lemonade server on /api/v1/health before dependent steps, instead of failing with Could not connect to Lemonade server.

hermes-lemonade-server and openclaw-lemonade-server lemonade-model-load had no readiness gate (every other lemonade playbook does); they now @require:lemonade-ready before loading.

Validated locally: the gate resolves and runs immediately before lemonade-model-load on windows + linux; validate_playbooks passes.

Refs #666, #668 (verify via nightly before closing).

Introduces a require-able readiness gate under a new dependencies/checks/
namespace (registry category: check). @require:lemonade-ready waits for the
Lemonade server on /api/v1/health before dependent steps, instead of failing
with 'Could not connect to Lemonade server'.

hermes and openclaw lemonade-model-load had no readiness gate (every other
lemonade playbook does); they now require it before loading.

Refs #666, #668.
@sreeram-11

Copy link
Copy Markdown
Collaborator

@lucbruni-amd,

I’d prefer to add this as a test in the README rather than introducing a new field in registry.json.

registry.json defines pre-installed software dependencies and setup steps for AMD Halo Developer Platform.

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.

2 participants