Add ZVMA pre/post script recipe + env-dump examples #18
Reference in New Issue
Block a user
Delete Branch "claude/modest-fermat-db665b"
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?
Adds a Kubernetes-ZVMA companion to the existing Windows-ZVM recipe:
pre and post phases, packages the Zerto* env vars into a structured
JSON body and POSTs to a {phase}-templated webhook URL.
that posts a Slack/Teams notification, with phase-aware formatting
and ZertoForce highlighted on pre.
receiver that pings + port-probes each VM in VmDisplayNames after
failover and writes a per-run JSON report.
env-dump client/receiver pair (the diagnostic that surfaced what
the ZVMA scripts-service container exposes).
the existing Windows-ZVM recipe's structure.
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
Adds a Kubernetes-ZVMA companion to the existing Windows-ZVM recipe: - scripts/examples/zerto-zvma-send.ps1 - Zerto-side sender for both pre and post phases, packages the Zerto* env vars into a structured JSON body and POSTs to a {phase}-templated webhook URL. - scripts/examples/zerto-receiver-notify.ps1 - server-side receiver that posts a Slack/Teams notification, with phase-aware formatting and ZertoForce highlighted on pre. - scripts/examples/zerto-receiver-vm-healthcheck.ps1 - server-side receiver that pings + port-probes each VM in VmDisplayNames after failover and writes a per-run JSON report. - scripts/examples/send-env-vars.ps1 + save-env-vars.ps1 - generic env-dump client/receiver pair (the diagnostic that surfaced what the ZVMA scripts-service container exposes). - docs/recipes/zerto-zvma-pre-post.md - full walkthrough mirroring the existing Windows-ZVM recipe's structure. - README.md and docs/README.md - link the new recipe and examples. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>