ci(deploy-examples): include avatar in matrix + wire LEMONSLICE_API_KEY#5839
Merged
Conversation
The avatar example shipped in #5834 was intentionally left out of CI deploy while its secret-provisioning story was pinned down. LEMONSLICE_API_KEY flows through the same secrets-file mechanism healthcare uses for OPENAI_API_KEY. Requires the LEMONSLICE_API_KEY GitHub Actions secret on the repo.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
The avatar example shipped in #5834 was intentionally left out of the CI deploy matrix while its secret-provisioning story was pinned down — that's why the workflow runs for the avatar PR didn't actually push a new build of the agent.
This adds `avatar` to the matrix and plumbs `LEMONSLICE_API_KEY` through the same `.env.deploy` secrets-file mechanism healthcare uses for `OPENAI_API_KEY`.
Prereq
`LEMONSLICE_API_KEY` needs to be set as a GitHub Actions secret on the repo (settings → Secrets and variables → Actions) before the next deploy. Today it's only set per-agent via `lk agent update-secrets` for local out-of-band deploys.
Test plan