deploy-to-ephemeral
Skill2 starsChanged 19 days agoApache-2.0View on GitHub
Deploy application to an ephemeral environment. Use when spinning up env, deploying to ephemeral, or testing in ephemeral. Handles pool check, namespace reserve, deploy, rollout verify, and pod health.
In this repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- manage-local-servicesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Image tags: MUST be FULL 40-char git SHA, not short (8 chars).
- Very specific: line 13
Kubeconfig: NEVER copy kubeconfig. Use --kubeconfig=~/.kube/config.e for ephemeral.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deploy to Ephemeral
Full ephemeral deployment from scratch. Uses devops persona (bonfire, k8s tools).
CRITICAL DevOps Rules
- Image tags: MUST be FULL 40-char git SHA, not short (8 chars). Quay only has full SHA tags.
- Kubeconfig: NEVER copy kubeconfig. Use
--kubeconfig=~/.kube/config.efor ephemeral. - ClowdApps: Main =
tower-analytics-clowdapp, Billing =tower-analytics-billing-clowdapp. - Only release YOUR namespaces:
bonfire_namespace_list(mine=true)first.
Inputs
| Input | Type | Default | Purpose |
app | string | tower-analytics | Application name |
image_tag | string | "" | Full 40-char git SHA (empty = latest) |
duration | string | 2h | Namespace reservation duration |
pool | string | default | Namespace pool |
component | string | main | main or billing |
Workflow
1. Load Persona
persona_load("devops")
2. Check Known Issues
check_known_issues("bonfire", "")check_known_issues("deploy", "")
3. Pre-Deployment
bonfire_pool_list()— list available poolsbonfire_namespace_reserve(duration="{{ duration }}", pool="{{ pool }}")— reserve namespace- Parse output for
ephemeral-xxxxxpattern
4. Dependencies (optional)
bonfire_apps_dependencies(component="{{ app }}")
5. Deploy
- If
image_tag:bonfire_deploy(namespace="{{ namespace }}", app="{{ app }}", set_image_tag="{{ image_tag }}") - For billing: use
--set-parameter tower-analytics-billing-clowdapp/IMAGE_TAG={{ image_tag }} - For main: use
--set-parameter tower-analytics-clowdapp/IMAGE_TAG={{ image_tag }}
6. Verify
kubectl_rollout_status(deployment="{{ app }}", namespace="{{ namespace }}", environment="ephemeral")kubectl_get_pods(namespace="{{ namespace }}", environment="ephemeral")
7. Error Recovery
- "no route to host" →
vpn_connect() - "unauthorized" →
kube_login("ephemeral") - "manifest unknown" → verify image in Quay with full 40-char SHA
8. Memory
memory_session_log("Deployed {{ app }} to {{ namespace }}", "Duration: {{ duration }}")
Output
Report namespace, deployment status, pod health (running/pending/failed), and quick commands for extend/release.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

