autonomic-bot
f283a371bb
Sanitized single-commit public mirror of recipe-maintainer. - Removed test-ssh/.testenv (live creds); added test-ssh/.testenv.example placeholders. - Removed plans/ and planned-updates/ (deployment-planning docs) so no client/ deployment domains appear in the public repo. - All other secret stores were already gitignored. - docs.coopcloud.tech retained as a submodule (public upstream).
36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
---
|
|
description: Deploy the local recipe checkout to the test instance
|
|
argument-hint: <recipe-name>
|
|
allowed-tools: [Bash, Read, Write, Glob, Grep]
|
|
---
|
|
|
|
# Recipe Deploy
|
|
|
|
Deploy the current local recipe checkout to the configured test instance using chaos mode.
|
|
|
|
The recipe name is: $ARGUMENTS
|
|
|
|
Read and follow the instructions in `.claude/commands/includes/logging.md`.
|
|
Read and follow the instructions in `.claude/commands/includes/guidelines.md`.
|
|
|
|
## Steps
|
|
|
|
1. **Get the domain and server for this recipe**:
|
|
```
|
|
python3 scripts/get_test_instance.py --recipe $ARGUMENTS
|
|
```
|
|
This outputs DOMAIN and SERVER for the active instance.
|
|
- If the recipe has no `recipe-info/$ARGUMENTS/recipe.toml`, tell the user to run `/recipe-init $ARGUMENTS` first and stop.
|
|
|
|
2. **Show current local recipe state** — run `abra recipe diff $ARGUMENTS` to show what local changes exist in the recipe checkout.
|
|
|
|
3. **Deploy with chaos** — run:
|
|
```
|
|
abra app deploy <DOMAIN> --chaos --force --no-input
|
|
```
|
|
- `--chaos` deploys the local checkout as-is, ignoring uncommitted changes.
|
|
- `--force` skips confirmation prompts.
|
|
- `--no-input` ensures non-interactive mode.
|
|
|
|
4. **Verify the deployment** — suggest running `/recipe-test $ARGUMENTS` to confirm the deployment is healthy.
|