feat: env-diff, verify-deploy and notify actions #6
No reviewers
Labels
No labels
auto-update
blocked
dependency
major
release-blocker
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Wi3eDigital/laravel-deploy-actions!6
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/env-verify-notify"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #3.
Summary
Three composite actions (
runs: using: composite, bash + curl + jq + git only). Eachaction.ymlis a thin wrapper: inputs reach the scripts only throughenv:, never through${{ }}insiderun:.env-diff/env-diff.shandlib/dotenv.awkare Aevana's.bin/env-diff.sh/.bin/lib/dotenv.awk. Only the comments changed, so the git-ref mode,--files,--baseline-fileandENV_DIFF_PATHall work as before.report.shholds the release body step frompublish_release.yaml:vX.Y.Zother thantag, or theprevious_taginput.<!-- env-changes:start/end -->. A rerun replaces it, and content outside the markers is kept.new_keys: JSON array computed withdotenv.awk, not parsed from the Markdown. It is written as[]first, so it is always valid JSON.report(multiline).previous_tag.fail_on_error: true; otherwise it logs a::warning::.fetch-depth: 0, documented in its README.release_id, it only computes the outputs.verify-deploy/verify-deploy.shplus these inputs:/versionas plain text or{"version": "..."}JSON.mode: containswith a configurablepath, for the legacy homepage grep.user_agent, defaultlaravel-deploy-verify/1.max_time.diagnose.extra_url, with its own path, attempts and delay (kima/portal's license host).Set-Cookievalues omitted.notify/jq:linkinput is sent asurl.tsis UTC ISO.dedup_keydefaults to<project>:<event>:<version>.eventmust be one of the 7 plan events.severitymust be info, warn or critical.reasonsmust be a JSON array.required: "true":POST /repos/{repo}/statuses/{sha}with<status_context>(defaultnotify/pre-prod) = success.Differences vs the Aevana / kima/portal / slight-exposure copies
kima-portal-deploy-verify/1, which is now theuser_agentinput. slight-exposure hasenv-diff.shbut noverify-deploy.sh; its deploy workflows grep the homepage, which is whatmode: containswithpath: /covers.publish_release.yamlis the same in all three, except for the closing check-env hint. Aevana and portal append it and slight-exposure does not, so it is now thefooterinput (default empty).jq, for the JSON/versionform, and checks forcurlandjqup front (exit 2)./and the configuredpathinstead of a fixed/version.VERIFY_ATTEMPTS=10,VERIFY_DELAY=10) maps toextra_urlwithextra_attemptsandextra_delay.Tests
tests/run.shruns plain bash tests (bats is not available locally), using a python3 stdlib stub server (tests/stub_server.py) that logs every request:new_keys, release body patching, idempotency (second run gives the same body), the footer, warning vsfail_on_error, and the API being down.Set-Cookieomitted, contains mode, user agent, diagnose, server down, and usage errors (exit 2). It also asserts the host never appears in the output..github/workflows/test_shell_actions.yaml:node:24-bookworm-slim@sha256:01d5…; node is needed because actions/checkout v7 is a node24 action. The job runsapt-get installfor git, jq, curl, python3 and shellcheck../notify,./env-diffand./verify-deploythroughuses:to exercise theaction.ymlwiring.Not verified
uses: https://forgejo.entwirr.me/Wi3eDigital/laravel-deploy-actions/<dir>@<sha>on Forgejo, includinggithub.action_pathresolving to the action directory. To be verified in the Aevana pilot. CI only covers localuses: ./<dir>.GITHUB_OUTPUTsets the same name twice.notifywritesdelivered=falsefirst, thentrue, and env-diff does the same withnew_keys; GitHub keeps the last one.🤖 Generated with Claude Code
https://claude.ai/code/session_0114prpbjyD3Bqt26YpZ1MEL