feat: ephemeral deploy, destroy, env list commands#3
Merged
Conversation
Adds CLI support for ephemeral environment lifecycle: - asobi deploy --ephemeral [--name N] [--json] — create fresh env (1h TTL) - asobi destroy <env_id> — delete env and revoke its keys (idempotent) - asobi env list [--ephemeral] [--json] — list envs for current game CI integration pattern (in README): wrap deploy with trap-based destroy so envs are cleaned up on test completion. Server-side reaper is the safety net if trap doesn't fire. Server-side: requires asobi_saas#22. Also: add 'asobi' build artefact to .gitignore.
Pre-existing local change. Larger Lua bundles can take longer than 30s to compile; bump timeout to 5min. Some engine versions return empty body on success — treat 2xx empty body as success.
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
Adds CLI support for the ephemeral environment lifecycle:
CI integration pattern
```bash
DEPLOY=$(asobi deploy --ephemeral --json)
ENV_ID=$(echo "$DEPLOY" | jq -r .env_id)
ASOBI_API_KEY=$(echo "$DEPLOY" | jq -r .api_key)
trap "asobi destroy $ENV_ID" EXIT
... run tests ...
```
The 1-hour server-side TTL is the safety net.
Server-side companion
Requires widgrensit/asobi_saas#22 (ephemeral env lifecycle + reaper).
Also included
Test plan